Hi Ben,
You may have better luck using Jibx2Wsdl:
http://www.sosnoski.com/jibx-wiki/space/axis2-jibx/jibx2wsdl You can
also see the article at
http://www.infoq.com/articles/sosnoski-code-first discussing "code
first" approaches in general, and Jibx2Wsdl in particular. Jibx2Wsdl
handles a wider range of inputs than Java2WSDL, and also supports
customizations to change the default generation process. You may find
that using the generated JiBX data binding also gives you a way to
easily use your existing data classes with Axis2.
I'll see about adding some links on this to the download documentation
for Axis2 1.4. There doesn't seem to be much point in recommending
people use Java2WSDL when there are many known limitations, and
Jibx2Wsdl does a better job all around. I'll also try to get the
documentation finished and a formal release of Jibx2Wsdl soon.
- Dennis
--
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Ben Reif wrote:
Duncan,
Thanks for the input. We're trying to incorporate the WSDL generation
into another automated process, so manually generating it with the
NetBeans IDE probably won't work for us. I have however, tried using
the WsGen tool as well, and I noticed a different problem, the
generated WSDL didn't indicate that the operations threw any Faults at
all. They were missing from the WSDL completely. Does anyone else have
any other thoughts or ideas?
Ben
On 12/20/07, *Thomson, Duncan* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
>-----Original Message-----
>From: Ben Reif [mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>]
>Sent: Tuesday, December 18, 2007 5:34 PM
>To: [email protected] <mailto:[email protected]>
>Subject: [Axis2] Java2WSDL with JAX-WS and JAXB annotations
>
>Hi,
>
>As I understand it, now the best way to re-use your existing
>code is to use the JAX-WS and JAXB annotations and then run
>your code through the Axis2 Java2WSDL utility passing in the
>"-sg" argument with the value "
>org.apache.axis2.jaxbri.JaxbSchemaGenerator". ....in theory should be
>portable to other platforms and tools as well.
>
FYI, Netbeans has very nice JAX-WS and JAXB support, and does a very
nice job of annotation processing. Note that if you use this you
don't
need Axis at all - instead of Java2WSDL the Netbeans IDE uses a
different set of tools - wsgen and wsimport, if I remember correctly.
You can also launch these tools directly yourself, and perhaps
they are
available within other IDEs, I'm not sure.
Anyway, the point is, as far as I can tell, with these tools, there's
really no need for Axis2. Perhaps someone else will explain why it's
needed, but I don't see it.
Duncan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
