[jira] Created: (XMLBEANS-299) Support substitution groups when the substitution is compiled in a different jar

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@...

    [ http://issues.apache.org/jira/browse/XMLBEANS-299?page=comments#action_12454562 ]
           
Erik van Zijst commented on XMLBEANS-299:
-----------------------------------------

For more information on this issue, please refer to the thread "Generating partial schemas" of 11/27/2006 on the xmlbeans user mailinglist.

> 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@...

    [ http://issues.apache.org/jira/browse/XMLBEANS-299?page=comments#action_12454832 ]
           
David Jencks commented on XMLBEANS-299:
---------------------------------------

I asked about this on 7/2/2006 and Radu replied in more detail than above on 7/27/2006.  In geronimo we have exactly this problem of needing to be able to extend elements with other elements that are not known at the time the "base" schema is compiled.

I worked around this in geronimo by:

-registering substitution group elements in each additional schema with my own code
-filtering validation errors by seeing if the alleged unknown element is in fact a member of the substitution group, using the registration info just mentioned
-processing all substitution group members by registering a handler for each possible element with a handler collection, and when the processing code reaches the subtitutable element it iterates through the handler collection giving each handler a chance.  The handlers use XmlObject.selectChildrenForQNameSet to look for the elements they are interested in.

This works but is inconvenient.

I certainly don't understand xmlbeans as well as Radu but I thought it would be possible to have additional schemas, as they load, register the new substitution group element in the data structure that track the substitution group elements.  I forgot where this data structure is, but I found it once :-).  

I think anyone who wants to use this feature would be happy to load all the schemas they wanted to use before processing any documents, and perhaps explicitly construct a SchemaTypeLoader or SchemaTypeSystem and probably call specific methods to register the extension schemas to get this to work.

So, I don't see why any code needs to assume anything is unknown by the time a document is parsed.

> 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@...

    [ http://issues.apache.org/jira/browse/XMLBEANS-299?page=comments#action_12454856 ]
           
Erik van Zijst commented on XMLBEANS-299:
-----------------------------------------

You're right David, you and I are trying to achieve the exact same thing, with this problem as a result. I'm not sure your solution will work for me too (would it involve additional work or adding redundant elements in the extension schemas by the person building the extension?).

For anyone who's interested, below are links to the aforementioned mailinglist threads:

http://www.mail-archive.com/dev%40xmlbeans.apache.org/msg00933.html
http://www.mail-archive.com/user%40xmlbeans.apache.org/msg01872.html

> 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@...

    [ 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: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

    [ 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@...

     [ https://issues.apache.org/jira/browse/XMLBEANS-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cezar Andrei reassigned XMLBEANS-299:
-------------------------------------

    Assignee: Radu Preotiuc-Pietro

> Support substitution groups when the substitution is compiled in a different jar
> --------------------------------------------------------------------------------
>
>                 Key: XMLBEANS-299
>                 URL: https://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
>            Assignee: 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.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

    [ https://issues.apache.org/jira/browse/XMLBEANS-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602525#action_12602525 ]

Christopher Hunt commented on XMLBEANS-299:
-------------------------------------------

Could there not be some manual declaration of other jars that have classes to be potentially used as substitution candidates? I obviously have no idea of how substitution candidates are handled within xmlbeans right now, but I would feel comfortable informing xmlbeans of the whereabouts of other dependencies.

I think my request is something like David's above.

Meanwhile can we see the xmlbeans substitution groups FAQ make mention of this current limitation? (perhaps also in the Javadoc)

Thanks again for such a great product.

> Support substitution groups when the substitution is compiled in a different jar
> --------------------------------------------------------------------------------
>
>                 Key: XMLBEANS-299
>                 URL: https://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
>            Assignee: 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.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...