AFAICT the CXF command-line wsdl2java statement does not have an option
for compiling unattached schemas in addition to WSDLs. But if you can
precompile your schema(s) using JAXB's xjc tool into a JAR you may have
a simpler question for the soapUI forum (http://www.soapui.org/forum),
namely how to include such JARs in the classpath when making SOAP calls.
Glen
On 1/10/2011 6:46 AM, Juan Pablo Pizarro wrote:
Glen, my command was:
./wsdl2java.sh -p uy.com.tcu.ws.client -d /home/jpp/tmp -compile -classdir
/home/jpp/borrar -client -all -ant -exsh false -dns true -dex true -validate
-verbose /tmp/tempdir1313337975435959979.tmp/Stock_1.wsdl
It was generated by soapUI. If i can, i will try the maven approach too.
Regards,
JP
2011/1/10 zahid<zahid.ebra...@uk.bnpparibas.com>
I am using Maven. I thought this too so initially so I did add an extra
step
to create the JAXB artifacts in the build - so basically my maven POM
looked
like this..
pom
dependencies
plugin - cxf-codegen-plugin (wsdl2java target to generate java from
wsdl)
plugin - maven-jaxb2-plugin (to generate java from xsd in
src/main/resources)
using the wbove two pplugins - I was able to generate java classes for both
the artifacts described in the wsdl and the xsd. I also (in code) used a
Marshaller to actualy check that the object created could be marshalled
ointo xml and it worked - the problem came when actualy making a sop
request
and passing the xsd described object as a paramenter to the soap call - I
was getting marshalling exceptoins telling me it did not have any knowledge
of the xsd described classes...
Z
--
View this message in context:
http://cxf.547215.n5.nabble.com/wsdl2java-with-external-xsd-binding-help-tp3329178p3334600.html
Sent from the cxf-user mailing list archive at Nabble.com.
