[ http://issues.apache.org/jira/browse/XMLBEANS-299?page=comments#action_12454991 ] Radu Preotiuc-Pietro commented on XMLBEANS-299: -----------------------------------------------
I have two comments on what David said: 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? 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 don't fully understand David's solution (as far as I know, the generated getters for substitutable elements have specific code in them to deal with substitutions, which is how we avoid paying the costs for non-substitution cases). But once I do understand, if both David and Erik are fine with this solution, then I guess it would be more than nothing so I'd be fine with it. > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
