[
http://issues.apache.org/jira/browse/XMLBEANS-299?page=comments#action_12457783 ]
Erik van Zijst commented on XMLBEANS-299:
-----------------------------------------
> 1. Last time I looked at the issue, the validation actually worked, it was just the binding that didn't work, are you saying that's not
> what you found?
Everytime I try it, the explicit validation I apply on the parsed document fails (MyDoc.Factory.parse() succeeds, but myDoc.validate() returns false). When I skip validation and just use the parsed document, it lacks all elements whose generated classes were in the extension jar. Instead, the getters return null.
> 2. Registering the extension Schemas explicitly in the code comes, in my mind, against the direction of being able to have the
> substituions in the extended Schemas integrate seamlessly in the current structure (the way everything else loads dinamically without
> needing to be known in advance).
I agree. Extensions on schemas and separately compiled stubs should integrate seemlessly. Therefore David's solution doe not work for me as I have no control over the extensions.
> Support substitution groups when the substitution is compiled in a different jar
> --------------------------------------------------------------------------------
>
> Key: XMLBEANS-299
> URL:
http://issues.apache.org/jira/browse/XMLBEANS-299> Project: XMLBeans
> Issue Type: Improvement
> Components: Binding
> Affects Versions: Version 2.2, Version 2.2.1
> Reporter: Radu Preotiuc-Pietro
> Fix For: TBD
>
>
> XMLBeans doesn't currently support substitution groups where the head element is compiled in a jar and the substitutions are compiled at a later time in a different jar.
> Because XMLBeans doesn't have the opportunity to save in the serialized xsb information about substitution groups (since these do not exist at the time the xsb is created) then it is forced to assume that any element can be a substitution for anything else and the only way to reliably tell is to load the element declaration. But loading the element declaration each time two elements are compared for QName equality is going to be very expensive even if loaded from the cache. This whole thing will need to be enabled on-request and have its separate codepath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...
For additional commands, e-mail:
dev-help@...
