This week's book giveaway is in the Servlets forum.
We're giving away four copies of Murach's Java Servlets and JSP and have Joel Murach on-line!
See this thread for details.
The moose likes Web Services and the fly likes SOAP Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "SOAP" Watch "SOAP" New topic
Author

SOAP

Robert Boyle
Greenhorn

Joined: Sep 28, 2005
Posts: 3
hi there - first post, be kind

I was wondering if it is possible to do the following:

Client A sends a soap request to Application B

Application B sends the soap reply to ThirdParty C?

Is this simple and straight forward if possible - or is it messy and not advisable?

Thanks.
R.
Pradeep bhatt
Ranch Hand

Joined: Feb 27, 2002
Posts: 8903

There are different MEP (Message Exchange patterns)that SOAP support.
1. Request/Response messaging (the normal one)
2. One way messaging (No response)
3. Notification
4. Solicitation/reply

Since Appplication A is not expecting any reply from App B , you could use one way messaging. One way messaging is usually implemented using document style messaging.

A calls B using one way messaging. B calls C.

Apache Axis has support for 1 & 2. So you may look there for more info.


Groovy
William Brogden
Author and all-around good cowpoke
Rancher

Joined: Mar 22, 2000
Posts: 12759
    
    5
Note that SOAP messages can be moved around by just about any transport mechanism you can imagine even though most examples use HTTP. For my SOAP book (now sadly outdated) I did examples with email and the JMS (Java Message Service) - basically anything that can move XML text will work.
Bill
Robert Boyle
Greenhorn

Joined: Sep 28, 2005
Posts: 3
Thanks guys.
Dave Haley
Greenhorn

Joined: Oct 11, 2005
Posts: 2
Hi guys, the main question here was about sending a call from A to B, and then to C. The typical SOAP implementation is based on HTTP, but if it were the case, both B and C would have to implement Web Servers isn't it? SOAP sounds great, but I am kinda tired of the idea that everything should be turned into a web service, and should be published using a Web Server, as if they were synonyms. However, everytime I read the basic introdution to what SOAP is they talk about SOAP being independent from transport, and that can be bound to other protocols besides HTTP. But then again, every time the go hands on, they start up their HTTP servers.

Originally posted by William Brogden:
Note that SOAP messages can be moved around by just about any transport mechanism you can imagine even though most examples use HTTP. For my SOAP book (now sadly outdated) I did examples with email and the JMS (Java Message Service) - basically anything that can move XML text will work.
Bill



This sounds promising, please, could you tell me where can I start from? Thnx in Advance
[ October 11, 2005: Message edited by: Dave Haley ]
 
wood burning stoves
 
subject: SOAP
 
Similar Threads
Help with SAAJ and SOAP 1.2
Adding attachments to web service response
Web Services->internal Proxy->External Soap EndPoint
Invoking JAX-WS method from browser
Using SwA in j2me clients