Hi guys, 

 

I have developed a simple web service that implements WSRF in muse and
deployed it successfully within an axis2 environment. The service comes
with a simple website that allows to create two resources and then call
the second from the first.  I am making the call with the standard proxy
that is generated by the framework. So far so good. 

 

Now I started to adjust the underlying axis2 configuration, in
particular I added a (http) proxy parameter to the HTTPTransport sender
in axis2.xml in order to make between the resources go through a proxy.
For my sample axis2 service this works as expected (ie call is sent via
the proxy) but for the muse service the option seems to have no effect.
I have double checked the axis2.xml in both scenarios and they are
identical apart from the  muse-wsa-action module. Can someone clarify,
could it be that this module impacts the way messages are sent out? 

 

Cheers

andi

Reply via email to