axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vishal Mehra <V.Me...@mdl.com>
Subject RE: "Chicken-Egg" problem with Java2WSDL/WSDL2Java
Date Mon, 07 Oct 2002 16:41:48 GMT
Thanks James,

Yes, one can provide the business logic either in SOAPBindingStub.java or
SOAPBindingImp.java but this does not solve the problem of moving the logic
from existing java classes to any one of the above classes. 

Is there an automated way to transform the existing java classes to
SOAPBindingImp.java? or an automated way to write wrapper (SOAPBindingImp)
classes on top of existing java classes?

-Vishal

-----Original Message-----
From: James Black [mailto:jblack@ieee.org]
Sent: Friday, October 04, 2002 8:52 PM
To: axis-user@xml.apache.org
Subject: Re: "Chicken-Egg" problem with Java2WSDL/WSDL2Java


Vishal Mehra wrote:

> I would like to expose e xisting java interfaces and classes via SOAP. 
> If  you run java2wsdl and then wsdl2java, you need to move logic from 
> existing classes to SOAPBindingImp.java. Ideally, I would like to keep 
> the logic in the original classes. Is there a way around?
>
  What I do is have a class, SOAPBindingStub.java and this is where I 
put my logic for the web service.  It also inherits the interface that 
was used for the java2wsdl call, so that the SOAPBindingImp class will 
just return what is in the stub.
  You can also use the stub when you run java2wsdl using --implClass.
  I hope this makes sense.




Mime
View raw message