Good point! Paul
On Mon, Dec 15, 2008 at 1:58 PM, Jaeger, Jay - DOT <[email protected]> wrote: >> Another model we are looking at is the "purl" model, where you >> actually point the client (in this case Synapse) directly at the >> Registry entry URL as a client. At the point of invocation, the >> Registry returns a redirect to the client, which then uses the >> redirected address from then on. Of course the redirect points to the >> real service. This is kind of nice approach, because it means you can >> use the Registry, with no special client code, for ANY client, as long >> as it obeys HTTP spec wrt redirects. > > However, if one were doing this without SSL (and maybe even with it), one > should be careful. I'd guess that it would be pretty easy to write a "man in > the middle" attack on such a use of a registry, returning a bogus endpoint > URL, and causing all sorts of havoc. > > JRJ > > > -----Original Message----- > From: Paul Fremantle [mailto:[email protected]] > Sent: Saturday, December 13, 2008 3:25 AM > To: [email protected] > Subject: Re: Synapse & Registry > > > David > > The WSO2 Registry team has written a handler that automatically > publishes WSDLs, XSDs, endpoints from any ?wsdl URL. So we can split > out the endpoints very effectively. We plan to build an endpoint > resolver for Synapse that will simply grab the URL from another URL > (the registry entry) and then use that. I would also like to complete > the UDDI work, but this approach seems cleaner. > > Another model we are looking at is the "purl" model, where you > actually point the client (in this case Synapse) directly at the > Registry entry URL as a client. At the point of invocation, the > Registry returns a redirect to the client, which then uses the > redirected address from then on. Of course the redirect points to the > real service. This is kind of nice approach, because it means you can > use the Registry, with no special client code, for ANY client, as long > as it obeys HTTP spec wrt redirects. > > Paul > > On Thu, Dec 11, 2008 at 12:00 PM, David Geary <[email protected]> wrote: >> Hi >> >> Is there any way to attach Synapse to a registry to allow it to dynamically >> resolve endpoint locations eg by specifying the portType. I know UDDI does >> this and there is no current support for UDDI, but is there any way to do >> this eg using the WS02 Registry? >> >> I know you can link to XSLT etc in an HTTP based Registry (including WSO2) >> but it would be nice to externalise the absolute address of services you are >> proxying to a central point, but this would require the registry to >> understand the concept of interface - endpoint mappings whereas currently >> WS02 registry just serves up resources? >> >> Not sure if this is best posted here or on a WS02 Registry list. >> >> Thanks for any help. >> >> Dave >> >> >> ________________________________ >> The information in this message is confidential and may be legally >> privileged. It is intended solely for the addressee. Access to this message >> by anyone else is unauthorised. If you are not the intended recipient, any >> disclosure, copying, or distribution of the message, or any action or >> omission taken by you in reliance on it, is prohibited and may be unlawful. >> Please immediately contact the sender if you have received this message in >> error. >> >> The views and opinions expressed in this email may not reflect the views and >> opinions of any member of Lagan Technologies Limited, or any of its >> subsidiaries. >> >> Lagan Technologies Limited is a company registered in Northern Ireland with >> registration number NI 28773. The registered office of Lagan Technologies >> Limited is 209 Airport Road West, Belfast, Co. Antrim, BT3 9EZ. >> >> > > > > -- > Paul Fremantle > Co-Founder and CTO, WSO2 > Apache Synapse PMC Chair > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [email protected] > > "Oxygenating the Web Service Platform", www.wso2.com > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [email protected] "Oxygenating the Web Service Platform", www.wso2.com
