any suggestions? :) is there any competitor open source that handles this?
maybe I shouldn't ask this here :) ________________________________ From: stoil valchkov <[email protected]> To: [email protected] Sent: Mon, November 30, 2009 9:22:03 PM Subject: Re: [castor-user] WSDL import - castor exception Castor still has this issue with default implementation of imports handling. This can be customized and fixed, but still there are other issues like referencing element definitions from xsd namespace which weren't that important for me and I didn't spent much effort there. Despite that at that moment castor was the best from open source I could find to handle xsd-s from wsdl :) adsfdsaf ----- Forwarded Message ---- From: Sasan <[email protected]> To: [email protected] Sent: Mon, November 30, 2009 5:39:49 PM Subject: Re: [castor-user] WSDL import - castor exception does this keep the issue open with Castor? you have posted this on 06, how did you resolve it? ________________________________ From: stoil valchkov <[email protected]> To: [email protected] Sent: Mon, November 30, 2009 5:25:11 PM Subject: Re: [castor-user] WSDL import - castor exception Hi, This was discussed some while ago http://markmail.org/message/pa35jxfizpes3d3c . Castor should be aware of that namespace and even ignore location if available. Regards, Stoil On Mon, Nov 30, 2009 at 6:31 PM, Sasan <[email protected]> wrote: Hi, > > >I am trying to parse the example provided in the link > >Listing4 which imports Listing 5 > >http://www.ibm.com/developerworks/xml/library/ws-tip-imports.html > >Note: I am providing the link only because the xml in question is slightly big >for copy paste here, I hope you don't mind. > >However I get the error when parsing the "Type" > >Unable to resolve Schema corresponding to namespace >'http://www.w3.org/2001/XMLSchema'. >org.exolab.castor.xml.schema.SchemaException: Unable to resolve Schema >corresponding to namespace 'http://www.w3.org/2001/XMLSchema'. >> at >> org.exolab.castor.xml.schema.reader.ImportUnmarshaller.<init>(ImportUnmarshaller.java:125) > at > org.exolab.castor.xml.schema.reader.SchemaUnmarshaller.startElement(SchemaUnmarshaller.java:604) > at > org.exolab.castor.xml.schema.reader.Sax2ComponentReader.startElement(Sax2ComponentReader.java:255) >> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown > Source) > at > org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) >> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) > at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) >> at >> org.exolab.castor.xml.schema.reader.SchemaReader.read(SchemaReader.java:301) ><more> > > >Is this a limitation introduced by castor? > >any info will be much appreciated. > >Thanks, >S. > > >
