Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
Message-ID: <002301c38cbf$c3915670$a365080a@vtpavan>
From: "vairamuthu thayapavan" <vtpavan@vijayaba.cse.mrt.ac.lk>
To: <axis-user@ws.apache.org>
References: <20031006210157.6027E6E0F1@smtp.us2.messagingengine.com>
Subject: Re: couple of questions
Date: Tue, 7 Oct 2003 16:42:53 +0600
Organization: lsf
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

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" <imhehenkamp@hotmail.com>
To: <axis-user@ws.apache.org>
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