+1. Current impl of Synapse taken for granted that xml coming into Synapse is via POST. If we can allow mediators to run on GET {from a switch, may be propagated from underline Axis2 listeners combine with a regex patterns} we can specify which mediators to run on which HTTP interface. If so, i believe we can support Glen's scenarios much more easily.

Saminda

On 4/20/06, Paul Fremantle <[EMAIL PROTECTED] > wrote:
Glen

I'm also +1. Should we think of it as mediating a generic XML/HTTP get? Or as a specific extension to Synapse just for WSDL and Policy?

Paul


On 4/19/06, Deepal jayasinghe <[EMAIL PROTECTED]> wrote:
Hi Glen ;

I am +1 on ur idea .

As you have mentioned we can change the address , in addition to that we
can change add new policy :)

Glen Daniels wrote:

>A thought - wouldn't it be cool if Synapse could mediate WSDLs as well?
>I could do something like:
>
>http://my-synapse.com/services/foo?wsdl
>
>And Synapse would take the WSDL at http://my-real-host.com/foo?wsdl,
>process it, and hand it back to the client.  In particular it would
>rewrite the addresses, and perhaps also add policy markup or even change
>the interface.
>
>Several steps might be used to get there:
>
>1) Trivial.  Simply register URLs and files that they correspond to.
>Something like:
>
><synapseConfig>
> <wsdls>
>  <wsdl url=""
>    ~/.synapse/wsdls/foo.wsdl
>  </wsdl>
> </wsdls>
> ...
></synapseConfig>
>
>2) Use URLs instead of files
>
>3) Figure out how to add WSDL processors to the above to add appropriate
>stuff
>
>(The problem here is that with the current "everything goes through the
>same chain of mediators" pattern, it's a little challenging to do #3.
>If you had a configured chain of mediators on a per-service basis, you
>might be able to just hand the WSDL to each mediator in turn for
>modifications.... I always did like the multiple-Axis-services model
>better :))
>
>Anyway, something to think about, even if only for the simple version.
>
>--Glen
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>


--
Thanks,
Deepal
................................................................
~Future is Open~


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

Reply via email to