A simple proxy service can be found at /samples/proxy .   if the code is
modified to set an alternative transport on the outbound call, you would
have a gateway.


/Chris


-----Original Message-----
From: Bi�rn Bi�rnstad [mailto:[EMAIL PROTECTED] 
Sent: Friday, February 20, 2004 7:44 AM
To: [EMAIL PROTECTED]
Subject: SOAP intermediary [was: How do you perform a transport protocol
change using Axis?]

Hi,

I have exactly the same problem. The solution to our problem is called
"SOAP
intermediary" (in this case a "forwarding intermediary"). But the next
problem
is: How do I implement an intermediary using Axis? I have read all
documentation
I could find, I have searched the mailing lists and the Web. But I found
absolutely nothing which would give me a hint on how to implement a SOAP
intermediary in a _clean_ way.

IMHO the Axis architecture (and especially all the documentation) is
somewhat
biased towards RPC. This is sad since Axis claims to implement SOAP and
not only
SOAP RPC. But I might be missing something...

Currently I'm trying to implement the intermediary as a normal web
service which
just forwards the raw message using an AxisClient engine. But this is
not the
way it should be done and I even don't know whether it will work in the
end.

I would very much appreciate if someone could comment on the problem of
SOAP
intermediaries and state what the status of Axis is regarding this
issue.

cheers,
Bioern

NICHOLLS T Ext OCISI wrote:
> Hello guys,
> 
> I have to do a transport protocol change when I send web services
requests and responses over the internet, from one intranet to another.
Internally on the intranets the web services communication will be SOAP
over HTTP, but when being transfered over the internet it should be send
as SOAP over JMS.
> 
> My idea for a solution is two create two "gateways" that can perform
transport protocol changes. The two gateways will be installed in Axis
based containers (in my case the Axis integrated in JOnAS) and the
actual gateway applications will be web services running in the two Axis
installations.
> 
> As far as I can understand it shouldn't be an issue to send SOAP over
JMS with Axis, but I haven't yet figured out whether or not I can do
this transport protocol change without modifying the message.
> 
> So my question is:
> Does anyone have any ideas or maybe even examples of how a transport
protocol change service for Axis could be created?
> 
> Regards,
> Thomas

-- 
Please reply to the newsgroup/mailinglist only.


Reply via email to