Hello,
We've got some strange problems with Java-XML binding using
Castor 0.9.3.21.
One of them is something like: we have a basetype B with required
attribute a. There is also type B1 which inherits from B
indirectly (with one intermediate type in the hierarchy), and it
redefines a as a fixed attribute. When marshalling, instances of
B1 type marshal the 'a' attribute twice, making it impossible to
unmarshal such file (Xerces parsing exception).
Another issue - we have a type A which defines an alternative.
One of the alternatives is a simple sequence of types D
(required) and E (optional). Another alternative is just a single
element of type E (required). But when defining an instance of A
with only E element set, such an instance cannot be unmarshalled
after marshalling. It seems that unmarshaller thinks that it
should be the first alternative and throws
UnmarshallingException: "D is required field".
The problem is that the schemas are externally defined and we may
not redefine them, so we urgently need a solution for these
problems. Is there anyone who could help?
Best regards,
Michal Plechawski
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
