I have run Axis 1.1 installed as a war under JBoss and JBoss-net services in the same
server instance without any trouble. Using JBoss-net (which is also built on Axis
1.1) has an advantange in that you don't need to mess with the Axis deploy/undeploy
descriptors or plug your apps under the Ax
I got it to work with authentication. From the locator I was getting my interface
(which extends the Remote). Instead I casted it, per your suggestion, to the stub:
AxisSoapBindingStub port = (AxisSoapBindingStub)service.getAxis();
| port.setUsername("blah");
|
Your method likely will not be named "getHello". In the Locator code generated by
wsdl2java, you should see a few methods that return your Stub. In mine, I see that
one method has no arguments and one takes a URL object as an argument to return the
Stub.
For example, I have web service named
nehring,
What is the getHello method? My locate doesn't have any access to my defined methods.
In the client code I'm doing the following below. Where first I get the locate, then
from it I get my EJB remote interface (that was generate from wsdl2java) where I can
call my defined methods. I'm
I would use code similar to below. The idea is to:
1) locate the SOAP service (wsdl2java should have generated a Locator)
2) Instantiate the stub class.
3) Set the username and password in the stub.
4) Make the SOAP call to a remote method.
The names of the Locator and Stub classes have been
