On Tuesday 07 December 2004 23:49, Michael Schuerig wrote:
> On Tuesday 07 December 2004 10:32, [EMAIL PROTECTED] wrote:
> > Have you looked at the Service constructors that take a WSDL? This
> > might be the best route for you, rather than using WSDL2Java. You
> > can build a client very simply.
>
On Tuesday 07 December 2004 10:32, [EMAIL PROTECTED] wrote:
> Have you looked at the Service constructors that take a WSDL? This
> might be the best route for you, rather than using WSDL2Java. You can
> build a client very simply.
Thanks for pointing this out. I didn't realize there was such a
co
Have you looked at the Service constructors
that take a WSDL? This might be the best route for you, rather than using
WSDL2Java. You can build a client very simply. For example (with a service
operation that returns a list of types):
...
import org.apache.axis.client.Call;
import org.apache.axis.
I want wsdl2java to generate code that interoperates nicely with code
that already exists in my application. Thus, I don't want it to
generate specific classes, but rather bind to my existing ones,
possibly using custom deserializers.
I can achieve this goal partly by these steps
- types are d
