You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You will find that doing substitutions on simple data types is probably going to cause a lot more issues. the Java type system is much more limited than the XSD one and hence the JAXB runtime needs all these annotations to figure out how to enforce the additional rules of the XSD model with Java properties. I wrote the plugin to simplify the Java class model where the attribute field would be of a complex type with possible sub type implementations. If you can create a repeatable test failure, I can have a look what happens in the XJC compiler.
Let me see if I can throw together an example, I'm not using Double, it's a complex type, but it's giving the same subclasses are not known to this context.
it seems that the element is generating incorrectly "@XmlElementRef" instead of "@xmlelement".
XSD:
The text was updated successfully, but these errors were encountered: