Hi Chinthaka, I've tested the ability for WSDLReader to accept jar: notation URLs, which it successfully does. No code change was needed for this, as they are already handled correctly by the underlying URLConnenction.
So for example, since .aar's are effectively .jar's, using String wsdlurl = "jar:file://location/myservice.aar!/my.wsdl"; will work with the usual woden code fragment : WSDLFactory factory = WSDLFactory.newInstance(); WSDLReader reader = factory.newWSDLReader(); DescriptionElement descElem = reader.readWSDL(wsdlurl); Note that the file: URL requires an absolute path to locate the jar/aar. Classloading/classpath is not involved. However, since the form is "jar:<location URL>!/<location within jar>", Http URLs could be used to locate the jar/aar file entry if necessary. Please let me know whether this meet your needs, or if you have any questions. Thanks. Kind Regards, Graham. Eran Chinthaka <[EMAIL PROTECTED]> wrote on 23/11/2006 13:13:21: > Is this resolved? Meaning will it work if I use jar scheme? > > When I read this thread I got he idea that it is not working. Please advice. > > Thanks, > Chinthaka > > Arthur Ryman wrote: > > > > Perhaps the XML parsers support new URL schemes? I know that java.net > > does let you register new scheme handlers. > > > > Arthur Ryman, > > IBM Software Group, Rational Division > > > > blog: http://ryman.eclipsedevelopersjournal.com/ > > phone: +1-905-413-3077, TL 969-3077 > > assistant: +1-905-413-2411, TL 969-2411 > > fax: +1-905-413-4920, TL 969-4920 > > mobile: +1-416-939-5063, text: [EMAIL PROTECTED] > > > > > > *"Jeremy Hughes" <[EMAIL PROTECTED]>* > > Sent by: [EMAIL PROTECTED] > > > > 11/21/2006 10:50 AM > > Please respond to > > [email protected] > > > > > > > > To > > [email protected] > > cc > > > > Subject > > Re: URIResolver requirement to return InputSource > > > > > > > > > > > > > > > > > > Weird, jar: URLs are a part of J2SE. Could you post some test code > > somewhere or stack traces. > > > > Cheers, > > Jeremy > > > > On 11/21/06, Graham Turrell <[EMAIL PROTECTED]> wrote: > >> I've done some experimentation with the jar: URLs and the simple resolver > >> using the woden JUnit test suite. The resolver is able to process jar URLs > >> but the DOM and xml schema parsers don't handle them correctly > >> (MalformedURLException citing the "!" character). > >> I'll look a bit deeper to see what could be done, including the > > WSDLLocator > >> approach. > >> I'm aware that the OASIS resolver supports the jar: notation and will find > >> out to what extent and whether this gives us an out-of-the box solution. > >> > >> Maybe we should consider whether we want (or can achieve) Woden as a whole > >> supporting the jar notation at its API, not just the resolver? > >> For example ought it to be possible to supply a jar: URL to > >> WSDLReader.readWSDL()? At the moment, my testing on readWSDL() shows it > >> doesn't > >> accept jar: arguments out of the box (we get the MalformedURLException > >> above). > >> > >> > >> Kind Regards, > >> > >> Graham. > >> > >> > >> > >> [EMAIL PROTECTED] wrote on 17/11/2006 09:51:23: > >> > >> > 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] > >> > > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > [attachment "signature.asc" deleted by Graham Turrell/UK/IBM] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
