Chathura
Another question! Can these URL handlers be plugged in later by a user
without changing the core code?
Paul
Paul Fremantle wrote:
I think it would be good to write a general XSLT URL handler. But
actually if there is a way of doing a Java URL handler, we could write a
better one for WSDL.
The problem with WSDL is choosing which is the best endpoint. If we
write a URL handler it can do the following logic:
* Look in the properties for an ordered list of preferred endpoints
(i.e.
wsdlPreferredEndpointList->echoSOAP12port_https,echoSOAP11port_https,echoSOAP12port_http1,echoSOAP11port_http1)
* If this property doesn't exist, apply an algorithm such as prefer
SOAP12 first, then SOAP11, HTTPS first, then HTTP.
That way we can have a pretty neat way of just getting back the URL.
I'd also like to have another handler that takes a URL and turns it into
a HTTP 302 redirect response. So effectively I could browse:
http://foo.com/resources/paul/myEndpoint?urlredirect
and be redirected to whatever URL was stored in the registry there.
Paul
Chathura C. Ekanayake wrote:
Hi Paul,
I have added URL handlers in the Registry to support virtual
resources. All registered URL handlers are invoked before get
requests. If a URL handler found a URL pattern that it can process, it
will intercept and process the request. I have used this to construct
resources for representing comments, comment collections, ratings,
etc. For example if get(...) is called with the URL
"/projects/wsas/clustering.doc;comments",a collection resource is
returned with the URLs of all comments on
/projects/wsas/clustering.doc resource. The
CommentCollectionURLHandler intercepts this request and builds the
comment collection resource.
I think we can use the same method for processing simple queries or
applying xslts. For example we can write a XSLTURLHandler to detect
the
http://foo.com/resources/paul/my.wsdl?xslt=/resources/general/url.xslt
URL pattern and apply the given xslt on the given resource and return
the result.
Thanks,
Chathura
Paul Fremantle wrote:
Folks
I'm sure someone already has a plan how to do this, but I'm wondering
if we have a way of associating logic with a query.
Here is what I'm thinking:
I have a WSDL stored in the registry - say
http://foo.com/resources/paul/my.wsdl
But I don't want the full WSDL, instead I want to run an XSLT that
extracts the SOAP12 HTTP endpoint URL:
http://foo.com/resources/paul/my.wsdl?url=soap12http
or maybe
http://foo.com/resources/paul/my.wsdl?xslt=/resources/general/url.xslt
Paul
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
Office: +1 646 290 8050
Cell: +44 798 447 4618
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
