[ http://jira.jboss.com/jira/browse/JBXB-5?page=history ]
Scott M Stark updated JBXB-5:
-----------------------------
Description:
Ok, so what I would like to see is that Adrian, myself and others provide as
freakishly complex as needed xml documents and the associated object model as
content that goes into the xml binding testsuite. We need to evolve the
associated schema and if necessary, external binding metadata to the point that
the xml to java binding is being completely driven by configuration outside of
the micro-container.
In terms of being completely ignorant of the java object model/schema
interaction, yes its true that the previous jaxb like frameworks were so
completely tied to single dtd/schemas there were not usable for the object
models we need to deal with. I'm open to having to tweak our object model
somewhat if needed to be completely schema driven. The key thing is that I'm
not willing to be restricted to a jaxb compatibile approach if it requires an
object model we are not willing to live with. Additional binding metadata
through schema annotations or an external jbossxb is fine to move beyond the
jaxb compatible model.
was:
Ok, so what I would to see is that Adrian, myself and others provide as
freakishly complex as needed xml documents and the associated object model as
content that goes into the xml binding testsuite. We need to evolve the
associated schema and if necessary, external binding metadata to the point that
the xml to java binding is being completely driven by configuration outside of
the micro-container.
In terms of being completely ignorant of the java object model/schema
interaction, yes its true that the previous jaxb like frameworks were so
completely tied to single dtd/schemas there were not usable for the object
models we need to deal with. I'm open to having to tweak our object model
somewhat if needed to be completely schema driven. The key thing is that I'm
not willing to be restricted to a jaxb compatibile approach if it requires an
object model we are not willing to live with. Additional binding metadata
through schema annotations or an external jbossxb is fine to move beyond the
jaxb compatible model.
> Evolve the schema driven binding to that needed by the pojoserver
> -----------------------------------------------------------------
>
> Key: JBXB-5
> URL: http://jira.jboss.com/jira/browse/JBXB-5
> Project: JBoss XML Binding (JBossXB)
> Type: Feature Request
> Reporter: Scott M Stark
> Assignee: Alexey Loubyansky
>
>
> Ok, so what I would like to see is that Adrian, myself and others provide as
> freakishly complex as needed xml documents and the associated object model as
> content that goes into the xml binding testsuite. We need to evolve the
> associated schema and if necessary, external binding metadata to the point
> that the xml to java binding is being completely driven by configuration
> outside of the micro-container.
> In terms of being completely ignorant of the java object model/schema
> interaction, yes its true that the previous jaxb like frameworks were so
> completely tied to single dtd/schemas there were not usable for the object
> models we need to deal with. I'm open to having to tweak our object model
> somewhat if needed to be completely schema driven. The key thing is that I'm
> not willing to be restricted to a jaxb compatibile approach if it requires an
> object model we are not willing to live with. Additional binding metadata
> through schema annotations or an external jbossxb is fine to move beyond the
> jaxb compatible model.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
