On Tue December 1 2009 10:58:21 am rmiyares wrote: > The online documentation mentions that java2ws supports jaxb and aegis > databindings. Does it also support xmlbeans?
Maybe. Not really sure. Most likely with the same configuration things you have for Aegis, it might work. Alternatively, with 2.2.4 and newer, you can add an @Databinding annotation to your SEI interface to specify it uses xmlbeans. That should also work without the configuration file. In any case, the code used by java2ws and the ?wsdl thing is the exact same code. Thus, the wsdl produced by ?wsdl would be the same so > Here is the basics of what I am doing (apache-cxf-2.2.3): > > 1) vendor xsd's -> xmlbeans using xmlbeans-2.4.0, mapping empty or poorly > defined namespaces to package names > 2) annotated java (1.5) web service code using the previously generated > xmlbeans as inputs and internal variables > 3) attempting to publish on jboss 4.2.3 using cxf > > My issue is that the auto-generated WSDL served by cxf on jboss has the > original namespace issues from the vendor xsd's. I need to find a way to > make the package to namespace substitutions in the resulting WSDL using the > cxf tools or deployment configuration. Any ideas? Does the java2ws tool > support the xmlbeans binding and package to namespace substitutions? Well, xmlbeans doesn't really allow us to muck with the generated schema. Thus, if we generated a wsdl with different namespaces than what xmlbeans expects, messages sent using that wsdl would not work. The best bet, really, is to use an xslt or something to process the vendor xsd's into something more usable prior to running xmlbeans on them. -- Daniel Kulp [email protected] http://www.dankulp.com/blog
