Problems with SOAP...

[Romain]

Hello everybody,

I want to have a program that do something like that:
1. A client sends a SOAP message to a servlet.
2. The servlet receives this message and gives it to a server (which is
installed on the same PC than the Tomcat server).
3. The server sends back the response to the servlet as a SOAP message.
4. The client receives the response from the servlet.

The communication between my client and my servlet is ok and works fine.
My problem is for the second step. I don't know exactly what kind of
mechanism I have to use to send from my servlet a SOAP message to a
local application (using the port 12345 for example) and get a SOAP
response. I also don't know how the code must looks like on the server
side in order to receive a SOAP message from the servlet (and send the
response).

Any help welcome! Thanks in advance.

Romain.

 

[Christopher Blunck]

Hello everybody,

I want to have a program that do something like that:
1. A client sends a SOAP message to a servlet.
2. The servlet receives this message and gives it to a server (which is
installed on the same PC than the Tomcat server).
3. The server sends back the response to the servlet as a SOAP message.
4. The client receives the response from the servlet.

The communication between my client and my servlet is ok and works fine.
My problem is for the second step. I don't know exactly what kind of
mechanism I have to use to send from my servlet a SOAP message to a
local application (using the port 12345 for example) and get a SOAP
response. I also don't know how the code must looks like on the server
side in order to receive a SOAP message from the servlet (and send the
response).

Any help welcome! Thanks in advance.

Romain.

Hi Romain-
Good question.

It really depends on what you need to do. If you'd like to expose
a Stateless Session Bean via SOAP, you can download and install
Apache Axis. In it you'll find a StatelessSessionBean provider,
which you configure by providing a JNDI name and how to build the
initial context. Axis serves most of what you'll need (most
notably plain old regular flavor java classes with static methods).
If you need to expose a Stateful Session Bean, use Apache SOAP,
which is out-of-date and no longer being maintained. The fact that
Axis does not incorporate a StatefulSessionBean provider is an
indication that they authors think very lowly of SSB
implementations.

Best of luck, and welcome to SOAP.

-c