You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Reinhard Nappert <rn...@juniper.net> on 2009/11/10 16:36:46 UTC
Best way to "proxy" soap requests...
Hi,
I implemented a Web-Service, which gets all the request parameters and depending on some values it may have "forward" this request (with some altered values) to a second Web-Service. My question is if there is some kind of framework available, which takes care of the proxying part. To me, it seems not very scalable if I write a SOAP Client, which I instantiate and call in case I have to proxy the request.
Thanks,
-Reinhard
Re: Best way to "proxy" soap requests...
Posted by Upul Godage <up...@gmail.com>.
Web services are supposed to be interoperable. Synapse is a standalone
installation driven by an XML configuration file which says what to do
with the messages. It should be able to accept messages from Axis 1 or
Axis2, manipulate and forward to any service.
On Wed, Nov 11, 2009 at 10:02 PM, Reinhard Nappert <rn...@juniper.net> wrote:
> No, I haven't. How does this interact with Axis 1.4 based services?
>
> -----Original Message-----
> From: Upul Godage [mailto:upulg.dev@gmail.com]
> Sent: Wednesday, November 11, 2009 11:28 AM
> To: axis-user@ws.apache.org
> Subject: Re: Best way to "proxy" soap requests...
>
> Have you seen Apache Synapse which is based on Axis2. You could do content based routing, altering the message, writing your own logic in a custom mediator to extend the framework etc.
> Check out the samples at http://synapse.apache.org/Synapse_Samples.html
>
> On Tue, Nov 10, 2009 at 9:06 PM, Reinhard Nappert <rn...@juniper.net> wrote:
>> Hi,
>>
>>
>>
>> I implemented a Web-Service, which gets all the request parameters and
>> depending on some values it may have "forward" this request (with some
>> altered values) to a second Web-Service. My question is if there is
>> some kind of framework available, which takes care of the proxying
>> part. To me, it seems not very scalable if I write a SOAP Client,
>> which I instantiate and call in case I have to proxy the request.
>>
>>
>>
>> Thanks,
>>
>> -Reinhard
>
>
>
> --
> http://upulgodage.com
>
--
http://upulgodage.com
RE: Best way to "proxy" soap requests...
Posted by Reinhard Nappert <rn...@juniper.net>.
No, I haven't. How does this interact with Axis 1.4 based services?
-----Original Message-----
From: Upul Godage [mailto:upulg.dev@gmail.com]
Sent: Wednesday, November 11, 2009 11:28 AM
To: axis-user@ws.apache.org
Subject: Re: Best way to "proxy" soap requests...
Have you seen Apache Synapse which is based on Axis2. You could do content based routing, altering the message, writing your own logic in a custom mediator to extend the framework etc.
Check out the samples at http://synapse.apache.org/Synapse_Samples.html
On Tue, Nov 10, 2009 at 9:06 PM, Reinhard Nappert <rn...@juniper.net> wrote:
> Hi,
>
>
>
> I implemented a Web-Service, which gets all the request parameters and
> depending on some values it may have "forward" this request (with some
> altered values) to a second Web-Service. My question is if there is
> some kind of framework available, which takes care of the proxying
> part. To me, it seems not very scalable if I write a SOAP Client,
> which I instantiate and call in case I have to proxy the request.
>
>
>
> Thanks,
>
> -Reinhard
--
http://upulgodage.com
Re: Best way to "proxy" soap requests...
Posted by Upul Godage <up...@gmail.com>.
Have you seen Apache Synapse which is based on Axis2. You could do
content based routing, altering the message, writing your own logic in
a custom mediator to extend the framework etc.
Check out the samples at http://synapse.apache.org/Synapse_Samples.html
On Tue, Nov 10, 2009 at 9:06 PM, Reinhard Nappert <rn...@juniper.net> wrote:
> Hi,
>
>
>
> I implemented a Web-Service, which gets all the request parameters and
> depending on some values it may have “forward” this request (with some
> altered values) to a second Web-Service. My question is if there is some
> kind of framework available, which takes care of the proxying part. To me,
> it seems not very scalable if I write a SOAP Client, which I instantiate and
> call in case I have to proxy the request.
>
>
>
> Thanks,
>
> -Reinhard
--
http://upulgodage.com