Making a webservice call using axis2

[Brett Daburn]

I am developing a client for a web service that is already existing. I got axis2 and created the code form the WSDL2Java from the web service's WSDL. I set all of the objects but now do not know how to make the call to the service.

The documentation provided from the web service vendor is in ASP.NET, however, I'm using Java. I was able to follow their example up until instantiating the proxy for sending the request to the web service and calling it.

This is the ASP.NET code I can't follow:

SingleSignOnService proxy = new SingleSignOnService();
try{
  string redirectURL = Proxy.Authenticate(ssoMessage);
}
...

How do I send out the request to get back the response URL in Java?






My Java code so far:

      SSOMessage ssoMessage = new SSOMessage();
      
      PartnerCredentialsType partnerCred = new PartnerCredentialsType();
      partnerCred.setToken("token");
      ssoMessage.setPartnerCredentials(partnerCred);
      
      IDType idType = new IDType();
      idType.setType(BusinessEntityType.NonPrintable);
      idType.setString("jdoe_ExtID");
      
      UserCredentialsType userCred = new UserCredentialsType();
      userCred.setID(idType);
      
      SingleSignOnRequestType ssoRequest = new SingleSignOnRequestType();
      ssoRequest.setUserCredentials(userCred);
      
      ssoMessage.setSingleSignOnRequest(ssoRequest);

[Duc Vo]

Originally posted by Brett Daburn:
This is the ASP.NET code I can't follow:

SingleSignOnService proxy = new SingleSignOnService();
try{
  string redirectURL = Proxy.Authenticate(ssoMessage);
}
...

In AXIS, it is service locator object. Should be something like (providing that your port name is "SingleSignOnService"

SingleSignOnServiceService service = new SingleSignOnServiceServiceLocator();
 
SingleSignOnService sso = service.getSingleSignOnService();
 
string redirectURL = sso.authenticate(ssoMessage);
 

[Peer Reynders]

Originally posted by Brett Daburn:
I got axis2 and created the code form the WSDL2Java from the web service's WSDL.

Axis2 WSDL2Java supports different styles of data binding which affects the style of objects that it generates. It defaults to ADB (Axis Data Binding).

If you have a look at the Axis 2 sample clients that are included in the distribution you will notice that ADB clients follow this pattern

// 1. Create the Stub to access the service (proxy if you like) (defaults to URL in the WSDL)
StockQuoteServiceStub stub = new StockQuoteServiceStub(
  "http://localhost:8080/axis2/services/StockQuoteService"
);
 
// 2. Create a request object (here a nested class named after the matching method)
StockQuoteServiceStub.GetPrice req = new StockQuoteServiceStub.GetPrice();
 
// 3. Populate the request object with all the necessary information
req.setSymbol("ABC");
 
// 4. Access the actual web method which returns a response object
StockQuoteServiceStub.GetPriceResponse res = stub.getPrice(req);
 
// 5. Extract the detail information from the response object
System.out.println(res.get_return());

ADB can get a bit confusing as complex types are often mapped to one class to represent the "type" and another class to represent the "element" (which contains the "type"). Example:

<complexType name="SOAPStruct">
  <sequence>
    <element name="varString" type="xsd:string"/>
    <element name="varInt"    type="xsd:int"/>
    <element name="varFloat"  type="xsd:float"/>
  </sequence>
</complexType>
<element name="myElement" type="tns:SOAPStruct"/>
 

In this case ADB will create a SOAPStruct class with the properties and a MyElement class which contains a SOAPStruct instance. This could potentially clash with your mental model because it wouldn't unreasonable to expect the MyElement class to have the varString, varInt, and varFloat properties, just as the myElement element has the varString, varInt, and varFloat subelements - instead you have to set the properties on a SOAPStruct instance and then place the SOAPStruct instance in the MyElement instance.
This is referred to as the "Expanded" generation mode (which is the default).
[ November 25, 2008: Message edited by: Peer Reynders ]

[Brett Daburn]

I really appreciate the help. I believe that I have it set up correctly and am sending the request correctly. However, I am getting a timeout. Is there anything special you need to do to send to https?

Start:
- Deploying module: metadataExchange - file:/C:/Documents and Settings/c02378/Desktop/axis2-1.4.1/lib/mex-1.4.1.jar
- I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect
- Retrying request
- I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect
- Retrying request
- I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect
- Retrying request
- Unable to sendViaPost to url[https://services.pj1.staging.printable.com/TRANS/0.9/SSO.asmx]
java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:507)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:546)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:140)
at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:130)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:542)
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:189)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:371)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:209)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:401)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at com.printable.services._1_0.sso.SingleSignOnStub.Authenticate(SingleSignOnStub.java:463)
at com.printable.services._1_0.sso.Test.main(Test.java:47)
org.apache.axis2.AxisFault: Connection timed out: connect
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:371)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:209)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:401)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at com.printable.services._1_0.sso.SingleSignOnStub.Authenticate(SingleSignOnStub.java:463)
at com.printable.services._1_0.sso.Test.main(Test.java:47)
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:507)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:546)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:140)
at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:130)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:542)
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:189)
... 9 more
Done.

Here is my code:

package com.printable.services._1_0.sso;
 
import com.printable.services._1_0.sso.SingleSignOnStub.BusinessEntityType;
import com.printable.services._1_0.sso.SingleSignOnStub.IDType;
import com.printable.services._1_0.sso.SingleSignOnStub.PartnerCredentialsType;
import com.printable.services._1_0.sso.SingleSignOnStub.SSOMessage_type0;
import com.printable.services._1_0.sso.SingleSignOnStub.SingleSignOnRequestType;
import com.printable.services._1_0.sso.SingleSignOnStub.UserCredentialsType;
 
public class Test
{
  public static void main(String[] args)
  {
    System.out.println("Start:");
    
    try
    {
      SSOMessage_type0 ssoMessage = new SSOMessage_type0();
      
      PartnerCredentialsType partnerCred = new PartnerCredentialsType();
      partnerCred.setToken("token");
      ssoMessage.setPartnerCredentials(partnerCred);
      
      IDType idType = new IDType();
      idType.setType(BusinessEntityType.NonPrintable);
      idType.setString("jdoe_ExtID");
      
      UserCredentialsType userCred = new UserCredentialsType();
      userCred.setID(idType);
      
      SingleSignOnRequestType ssoRequest = new SingleSignOnRequestType();
      ssoRequest.setUserCredentials(userCred);
      
      ssoMessage.setSingleSignOnRequest(ssoRequest);
      
      SingleSignOnStub ssoStub = new SingleSignOnStub();
      SingleSignOnStub.Authenticate auth = new SingleSignOnStub.Authenticate();
      
      SingleSignOnStub.SSOMessage_type0 type = new SingleSignOnStub.SSOMessage_type0();
      type.setPartnerCredentials(partnerCred);
      type.setSingleSignOnRequest(ssoRequest);
      auth.setSSOMessage(type);
      
      SingleSignOnStub.Authenticate req = new SingleSignOnStub.Authenticate();
      req.setSSOMessage(ssoMessage);
      
      SingleSignOnStub.AuthenticateResponse res = ssoStub.Authenticate(req);
      System.out.println("! " + res.getAuthenticateResult());
    }
    catch(Exception e)
    {
      e.printStackTrace();
    }
    
    System.out.println("Done.");
  }
}

[Peer Reynders]

Originally posted by Brett Daburn:
Is there anything special you need to do to send to https?

According to this document (Accessing Web Service via SSL) you have to first import the server certificate into a client truststore

$JAVA_HOME/bin/keytool -import -alias tomcatCert -file tomcatserver.cer -keystore clientTrustStore

and then set some client properties

public static void main(String[] args) throws Exception{
   .....
   .....
   System.setProperty("javax.net.ssl.trustStore","/usr/lib/ooo-1.1/program/clientTrustStore");
   System.setProperty("javax.net.ssl.trustStorePassword", "changeit");
   ....
   ....      
}

[Brett Daburn]

Thanks for the info Peer. Does it look like this is the reason for the timeout? I mean, do you get a timeout exception when you don't have the certificate in your TrustStore? I changed it to not use https and am still getting the timeout when you can place the URL in the browser without the https and still get a response.

[Brett Daburn]

I just tried making a simple get request using the following code sample and got the same timeout exception. I will need to figure out what is wrong with my environment not allowing requests. Then I will look into the certificate issue. Thank you for your help!

[Peer Reynders]

Originally posted by Brett Daburn:
I just tried making a simple get request using the following code sample and got the same timeout exception.

A SOAP endpoint doesn't have to respond to GET requests. SOAP requests are POSTed to the SOAP endpoint URI.
A well behaved SOAP endpoint would return 405 "Method Not Allowed" - however some SOAP stacks have a bit of tunnel vision when it comes to following proper HTTP etiquette.

Finally http is typically served on port 80 while https (SSL/TLS) is served on port 443. So it is entirely possible that nobody is listening on port 80 even when port 443 works.

Simply point your browser to the URL that is composed of the endpoint address and a "?wsdl" suffix

https://www.xignite.com/xQuotes.asmx?wsdl

If the WSDL comes up it's likely that something is listening. If it doesn't come up the WSDL is suppressed or the server is down.
[ November 28, 2008: Message edited by: Peer Reynders ]