You obviously missed my point about the generated SchemaBInding not matching the xsd.
I've fixed all this.
I've also made it so there are top level schemas for javabean 1.0, 2.0 and the MC 1.0
and 2.0
the 2.0 and 1.0 were completely missing. For the javabean 1.0 i've disabled
the constructor element as per schema. It would be too much effort to
retrofit the classes such that we can generate a proper 1.0 schema that matches the xsd
(although I did do it for the top level deploymen element).
For 3.0 we need to properly control how these metadata classes evolve.
Anyway, I re-opened the issue.
This work isn't complete until we use it (rather than just testing :-).
Work still to do:
0) Do the same thing to the PolicyMetaData/parsing
1) Get a jbossxb release that includes these schemas in the factory settings
(see the singleton schema resolver bootstrap code)
2) Remove the old SchemaBindingInitializer
3) Co-ordinate with Kabir for the aop parsing and update the Spring parsing.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133172#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...