Compiling a Castor schema creates a different class hierarchy depending on the elements of the schema

When I save the castor-based system, I modify the original schema to create a new set of classes and find that introducing a new element creates a different class hierarchy. This applies to any type of item.

In short, the current schema creates a class foothat extends fooParent, which extends fooGrandparent. Add a new element to a schema that is not associated with these classes, and now Castor creates fooANDs fooParentthat expand fooGrandparent.

Has anyone seen this before?

+3
source share

Source: https://habr.com/ru/post/1699416/


All Articles