axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From doug <ummmm...@yahoo.com>
Subject Re: "Chicken-Egg" problem with Java2WSDL/WSDL2Java
Date Mon, 05 Aug 2002 15:58:59 GMT
so is it in the plans to allow a service to specify it's WSDL directly 
rather than having to reconstruct it from meta-information?

Tom Jordahl wrote:
> FYI
> If Axis doesn't emit the beans, there will not be any meta-information in them to tell
the runtime various WSDL specified attributes.
> 
> That may (or may not) be a problem.
> 
> --
> Tom Jordahl
> Macromedia
> 
> 
> -----Original Message-----
> From: Stuart Thomson [mailto:stuart@swtsoftware.com]
> Sent: Saturday, August 03, 2002 11:27 AM
> To: axis-user@xml.apache.org
> Subject: Re: "Chicken-Egg" problem with Java2WSDL/WSDL2Java
> 
> 
> Another option might be --rpc to generate only the classes required for
> the jaxrpc and soap stuff, ie stub, skeleton, service and service locator.
> 
> This would be more in line with the code generated by other remoting technologies.
> 
> I have no intention of letting axis mess with my lovingly hand crafted beans.

<snip history>


Mime
View raw message