Ok thanks, so if I understand correctly, I first have to use java2wsdl to generate a wsdl file from my interface-class and then I have to run wsdl2java to generate those classes from my wsdl file? Isn't there a solution to do it in one step?
Ilja On Tue, 7 Oct 2003 16:42:53 +0600, "vairamuthu thayapavan" <[EMAIL PROTECTED]> said: > hi > u can't do any thing with having the wsdl file only. to deploy your > webservice u have to generate server binding stubs using wsdl2java tool. > those are discribed detaily in the axis userguide. > > regards > vtpavan > ----- Original Message ----- > From: "Ilja" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, October 07, 2003 3:01 AM > Subject: Axis: couple of questions > > > Hi, > > I tried generating a wsdl file succesfully with my ant-build script from > an interface. However some things are not quite clear to me: > > - Can you also publish your webservices in your own webapp, without > deploying it in the axis webapp? > - Shouldn't more files be generated? eg like these?: > > WidgetPriceSoapBindingImpl.java : Java file containing the default > server implementation of the WidgetPrice web service. > > > You will need to modify the *SoapBindingImpl file to add your > implementation (see > ../samples/userguide/example6/WidgetPriceSoapBindingImpl.java ). > WidgetPrice.java: New interface file that contains the appropriate > java.rmi.Remote usages. > > > WidgetPriceService.java: Java file containing the client side > service interface. > > > WidgetPriceServiceLocator.java: Java file containing the client > side service implementation class. > > > WidgetPriceSoapBindingSkeleton.java: Server side skeleton. > > > WidgetPriceSoapBindingStub.java: Client side stub > > - I now have only a wsdl file and I'm pretty sure that's not enough to > publish my own webservices, more classes are needed right? > > Thanks, > > Ilja > > > > > >
