I think having XmlBeans support would be great, but I'm confused by
your footprint motivation. After a quick inspection, XmlBeans is
~2.7 times as big as Jaxb impl:
[01:50:46] dain$ ls -lh ~/.m2/repository/com/sun/xml/bind/jaxb-impl/
2.0.5/jaxb-impl-2.0.5.jar
-rw-r--r-- 1 dain dain 769K Jun 24 13:38 /Users/dain/.m2/
repository/com/sun/xml/bind/jaxb-impl/2.0.5/jaxb-impl-2.0.5.jar
[10:41:51] dain$ ls -lh ~/.m2/repository/org/apache/xmlbeans/xmlbeans/
2.3.0/xmlbeans-2.3.0.jar
-rw-r--r-- 1 dain dain 2M Oct 19 22:16 /Users/dain/.m2/
repository/org/apache/xmlbeans/xmlbeans/2.3.0/xmlbeans-2.3.0.jar
And since Java6 includes JaxB, overtime you will be able to drop that
also.
Anyway, I think having XmlBean support is cool... I'm just a bit
confused about the footprint comment.
-dain
On Dec 13, 2007, at 8:19 AM, mraible wrote:
We are currently using XFire in the AppFuse project and it works
great.
We are aware that Apache CXF is the next generation of XFire.
However, we've
also optimized the XFire footprint[1] to be as small as possible.
Part of
this optimization was removing JAXB 2 support and using XMLBeans
instead.
The XFire Migrating Guide[2] says that XMLBeans will be supported
in CXF
2.1.
What is the timeline for a 2.1 release?
Thanks,
Matt
[1] http://issues.appfuse.org/browse/APF-797
[2] http://cwiki.apache.org/CXF20DOC/xfire-migration-guide.html
--
View this message in context: http://www.nabble.com/Upgrading-from-
XFire-to-CXF-tp14319236p14319236.html
Sent from the cxf-user mailing list archive at Nabble.com.
