Hi,
I am a new user to Axis.
My question is, given that I have a class which I need to expose as a web service,
Do I need to have an interface over it to deploy it as a web-service?
I need to have the stubs/skeletons to be generated so that the client accessing my service can do so easily.
I have been looking at the WSDL2Java command, which generates a interface of the port name.So I need to make sure that the port name is different than that of the impl class(by using the -P option in Java2WSDL),but then before deploying the Web service,I need to modify the impl class to have an "implements port-name interface" in it.
This is so because the skeleton always tries to do an,
PortNameInterface impl = new ImplClassName(),
kind of instantion.
Even if the use the '-S false' option in WSDL2Java command a stub is
still generated,
which will implement the PortNameInterface.
So is it right to assume that if one wants a RMI type(involving stub/skeleton) calling mechanism for the client to call a web service, we need to have an interface for the main class for that web-service??
Thanks,
Chinbaj
How low will we go? Check out Yahoo! Messengers low PC-to-Phone call rates.
