more
flexible.
Cheers,
==>Lancer---
> -Original Message-
> From: Michele Costabile [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, July 12, 2001 3:39 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Client Code generator ..
>
>
> > Hen, not to d
Message-
From: Michele Costabile [mailto:[EMAIL PROTECTED]]
Sent: 12 July 2001 11:39
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Client Code generator ..
> Hen, not to discourage since what I am working on is vapor since it hasn't
> been released, but I am porting a WSDL2 Axis
lt;[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, July 12, 2001 6:38 AM
Subject: Re: Client Code generator ..
> > Hen, not to discourage since what I am working on is vapor since it
hasn't
> > been released, but I am porting a WSDL2 Axis Client proxy (from another
>
> Hen, not to discourage since what I am working on is vapor since it hasn't
> been released, but I am porting a WSDL2 Axis Client proxy (from another
> source base) which I hope to have working with primitive types by the end
of
> the week (and damn that end is coming up fast :-().
I would be ve
#x27;;
> [EMAIL PROTECTED]
> Subject: RE: Client Code generator ..
>
>
> Lance, correct me if I'm wrong, but you are working on WSDL2Java
> functionality only, correct? (i.e. given a WSDL document,
> generate Java
> proxies.)
>
> As I read Henner's messa
Lance, correct me if I'm wrong, but you are working on WSDL2Java
functionality only, correct? (i.e. given a WSDL document, generate Java
proxies.)
As I read Henner's message, he seems to be talking about Java2WSDL type
functionality (given a Java class, render WSDL for it), which I would
persona
Hen, not to discourage since what I am working on is vapor since it hasn't
been released, but I am porting a WSDL2 Axis Client proxy (from another
source base) which I hope to have working with primitive types by the end of
the week (and damn that end is coming up fast :-().
At any rate, this is
The relationship between Apache SOAP and Axis is similar to that between
JServ and Tomcat. Axis will ultimately be the preferred (and presumably
faster and more feature rich and stable) implementation. However, it is
hard to predict the point at which a critical mass of users will move to
Axis.