We Keep Coding

How does it internally work when a SOAP web-service is called?

I am new to SOAP web services. I am learning it from Youtube videos on my own. I have a doubt that how web service internally works.
I know(i might be wrong) there are overall of 3 steps :
1. A SOAP request is created at client end.
2. The SOAP request is sent over network through HTTP/UDP.
3. Server processes the SOAP request and sends back the SOAP response.
I think these 3 steps must be divided into sub-steps. So could anyone help me knowing what internally happens when a web service is invoked please.
Complete step from request generation to response received would be helpful.
As we know there is a standard question how hashmap works, if i can get the answer the same way then it will really be very helpful.
Thanks in advance!

Jasper server Report Service

I have JSESSIONID that i get from JasperReports Server RestAPI POST call. How can i use this sessionID for the future Report Service API calls? I am using REST API. Can any one give me a sample or any source code or any solution for this. I dont want to create LDAP/CAS for singllr-signon business. Please help me to trouble shoot this in Java.
Steps that i followed:
1. created session using JasperReports Server POST rest api call
2. tried to use that sessionID in the future /report service.

Add new header "cookie", and set value = JSESSIONID, send your further request with the header.

JAX-WS session management

I have been trying to maintain user session in a standalone JAX-WS client. The server code is as explained in https://weblogs.java.net/blog/ramapulavarthi/archive/2006/06/maintaining_ses.html.
My problem is with the client. The server does send the JSESSIONID with the response. But it looks like that the client's calls do not send the JSESSIONID with the request(I have tested this on TCPMon). Because of that the server creates a new session every time a request comes.
After some googling I found that I had to set BindingProvider.SESSION_MAINTAIN_PROPERTY = true in request conext in order to maintain user session in client. But sadly this also is NOT working for me.
I have tried generating the stub using AXIS and the session here is being properly maintained.
The web service has been deployed in Tomcat.
Thanks.

Axis 2 (1.6.1) client webservice Basic Auth

I´m trying to implement a client webservice (AXIS 2 1.6.1) in JBoss 5.1.0 GA.
I´ve generated the stubs and the first invocation (to a mockService) works fine.
Now i want to invoke my web service (without the mockService) and i need to inplement the Basic-Authentication.
I already implements the basic authentication code and i´m almost sure that there isn´t a bug in the code.
HttpTransportProperties.Authenticator basicAuth = new HttpTransportProperties.Authenticator();
basicAuth.setUsername("userName");
basicAuth.setPassword("password");
basicAuth.setPreemptiveAuthentication(true);
stub._getServiceClient().getOptions().setProperty(HTTPConstants.AUTHENTICATE, basicAuth);
Since i can make a invocation using the SOAP UI, i strongly believe that my problem is that i haven´t set my
"WWS-Password Type" and "WWS TimeToLive" (i have the same error message when i disable these properties on the SOAP-UI).
I think that i may need to put a axis2.xml in the server to put these properties but...
When do i put my configuration file (in JBoss)? Or where do i define the path to this file?
Or there is something else?
Thanks all.
Note: I tried unsucessfully this solution:
Adding User/Password to SOAPHeader for WebService client call with AXIS2
My error is:
Exception in thread "main" org.apache.axis2.AxisFault: Internal Error (from server)
at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:375)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at myPackage.process(MyStub.java:187)
P.S- Note that the server web service communicate over https.
P.S.2 - Tks Edward

Just for the record, i´ve resolved the problem using the solution in Adding User/Password to SOAPHeader for WebService client call with AXIS2 .
I had a misspelled tag (in this case, the user tag).
Thanks a lot.

Consuming a WCF service in a Java Client using wsHttpBinding

I'm trying to get a Java Client to communicate with a WCF wshttpbinding WebService. But I've been unsucesful so far. The call either hangs, or I get: “SOAPFaultException: The message could not be processed. This is most likely because the action 'http://tempuri.org/ISampleService/GetServiceName' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding.”
My Web Service is just the default Visual Studio 2010 generated "WCF Service Library Template".
My java client is generated in netBeans 7.0.1 and stubs have been generated using new Other --> Web Services --> Web Service Client and I’m referencing a local WSDL.
I've tried adding WebServiceFeature wsAddressing = new AddressingFeature(true); in the stub generated but it just throws the exception above.
I see other people with similar problems; however, I don't see any true resolution. Any suggestions would be greatly appreciated.

It sounds like you have a soap formatting issue. The java client isn't generating soap XML that makes sense to the WCF service. To get an idea of what the soap XML the service is expecting use the WcfTestClient command line app to call the service. This app dynamically creates a service proxy in a WinForm app. In the app, call the service operation and click the XML tab (next to the Formatted tab at the bottom of the right pane). You'll see both the request & response soap in this tab.
Next, configure the WCF service for message tracing and call it from the java client to see the soap XML it is being sent. Now you can compare the two soap messages to see what is different. The java client will need be configured to generate the soap format the WCF is expecting.
The WCF team recently released some WCF interop bindings specifically for java. These may not apply to your specific situation but they're probably worth reviewing.