[opencms-dev] XSD's

[Atle Enersen]

Hello Kai.

It is not Mysql, there are so many databases running on it that it would trigger som error on other apps. I cannot just upgrade Mysql. An upgrade will potentially destroy database(s).

The SAX parser config is already sat to false.

When I take a content class of mine and make it usable for Mercury it trigger the unmarshalling-error.

I have already done the step-by-step both removable and add more fields. Same error.

I can turn debugging on, I just do not know how. I think that would give us additional info. Today we do not know which file or where in the file the unmarshalling-error gets triggered.

Do you want to have a peek "under the hood" of the OpenCms installation?

Best regards Atle Enersen
--
Tel.: +47 48063171
Bluesky/X-Twitter: @nesrene

-----Opprinnelig melding-----
Fra: Schliemann, Kai <K.Schliemann at comundus.com> 
Sendt: onsdag 17. januar 2024 17:59
Til: Atle Enersen <atle.enersen at gmail.com>
Kopi: opencms-dev at opencms.org
Emne: AW: [opencms-dev] XSD's

Hello Atle,

difficult issue. 
Your MySQL version is quite old, but I doubt, that this is a problem. So if it is easy for you to replace it with an newer version, give it a try.
One more thing you could check is the SAX parser config in OpenCms as described here:
https://documentation.opencms.org/opencms-documentation/server-administration/tomcat-configuration/index.html#improving-xml-unmarshalling-performance-22cb94f4
We never use this option, so if it is set to true, change it back to false and restart Tomcat.

If all this does not help you could try one more thing.

Create a new content type and add the fields from your old / "broken" schema files to the new schema file. Make all the necessary steps to make it available to the content editor and try to add a new content item of this new type. 
Doing this I would suggest to start very simple.
So create the new schema with just one field.
Add field by field.
Leave out nested schemas and configurations in the first place.
Between each step, try to place new content type to the page and see if everything works.
If you are lucky, the error never appears with the new content type.
But if it does, you should be able to find the field or the config, which is responsible for the problem.
You might need to dig into a nested schema. Maybe the problem is there.

Last hint:
If you have the possibility for debugging this could help you finding the problem as well.
Good luck.
Best regards
Kai