On 11/16/06, John Kaputin <[EMAIL PROTECTED]> wrote:
Graham, I discussed this Axis2 requirement with Chinthaka tonight. We will probably need a call with you on Friday to discuss further. The URIResolver interface has a resolveURI method that takes a URI and returns a URI. Axis deployed AAR files need to bundle the WSDL and schema files but in this case Woden cannot read them because it cannot resolve URIs to the contents of these types of archives.
Does the jar: URL/URI scheme work here? [1] after all isn't an aar file just a jar renamed. [1] http://java.sun.com/j2se/1.4.2/docs/api/java/net/JarURLConnection.html
Axis can provide this behaviour, but they need a resolver mechanism with an API that takes a URI but returns an InputSource - e.g. a URIResolver method like "InputSource resolveURI(originalURI)". The way this works in WSDL4J is the WSDLLocator interface. WSDL4J provides this interface and the WSDLReader accepts a WSDLLocator object and makes use of it when importing other wsdls or schemas, but the client application (e.g. Axis or WSIF) provide the WSDLLocator implementation.
While the WSDL4J WSDLLocator mechanism is more flexible (and more complex) I think jar: works for most cases.
The solution might be to do something similar with the URIResolver interface or something like it. You mentioned a while back that URI to URI resolution was just the start and that resolving URIs to other things (e.g. InputSource?) might be required. I'd like to discuss your thoughts on this wrt the Axis requirements. Can we discuss further on Friday. Maybe a phone call with Chinthaka too. Will be in touch Fri.
I'd like to dial in too.
John Kaputin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
