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="services/foo?wsdl"> > ~/.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]
