Well, I know there are a couple of Progress/FUSE customers that are using the XmlBeans databinding for production level things. Thus, it's definitely usable for some scenarios. Thus, if you are having issues, please file jira bugs and attach test cases if at all possible. That said, I DO think they are using JAX-WS + XmlBeans almost entirely.
One note though: there are several fixes for xmlbeans on the latest branches. If you can tests with that, that would be great. That said, our hudson server is having issues so there aren't recent snapshots so if you cannot, don't stress it. :-( Dan On Tue July 21 2009 7:37:36 pm [email protected] wrote: > What is the real status with regards to XmlBeans support in CXF and is > it the right time to start porting from XFire/XmlBeans to CXF/XmlBeans > ? > > I have a large amount of code that uses XFire with XmlBeans and a > document/java first approach. I would like to port as XFire is not > really supported for some time now and we have had to make a few > patches to it to fix some issues. Further, we would like to also > expose some services as REST so CXFs support for JaxRs is nice. > > The reason I ask is that I have protoyped a little test application > using a java/document and while things work in the simple case, I > cannot get the sending of a soap header to work. I did manage to > receive and process the SOAP header on the server side, but only when > I switched to JaxWsServerFactoryBean. Obviously JaxWs is the way to > go but I was hoping to port with the minimal amount of code changes in > the first instance. > > If it is considered that CXF/XmlBeans is ready (despite the out of > date wiki status/roadmap pages) then I perhaps may post some more > specifc issues that I have. > > David -- Daniel Kulp [email protected] http://www.dankulp.com/blog
