The original versions were crap, that is unless you never wanted to change
your schema/code.
And you also had to do a precompilation stage to generate your parser.
The latest version has resolved many of these issues, although there
are still a number of features missing, e.g. dynamic wildcard handling
like JBossXB can do.
e.g. the recent spring integration code lets you mix and match
JBoss MC and Spring xml in the same file:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <deployment xmlns="urn:jboss:bean-deployer:2.0">
|
| <bean name="oldBean"
class="org.jboss.test.spring.support.OldBean">
| <property name="testBean"><inject/></property>
| </bean>
|
| <bean xmlns="urn:jboss:spring-beans:2.0" id="testBean"
class="org.jboss.test.spring.support.SimpleBean">
| <property name="mylist">
| <list value-type="java.lang.String">
| <value>onel</value>
| <value>twol</value>
| <value>threel</value>
| </list>
| </property>
| </bean>
|
| </deployment>
|
I'd also need to do a lot more testing before I was convinced it actually works.
e.g. I recently filed a bug which shows Sun's impl doesn't inheritance properly.
I've been assigned a bug number, but it hasn't appeared on the website yet
- who knows when it will get fixed, hopefully not 4 years like the classloader
problems :-)
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6516905
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005861#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...