Thanks for your response. The messages appear from calling the passed error handler's getErrorMessages() method so I'm assuming they're errors.
I think you are misunderstanding my first message. An example of one of the import tags in the WSDL is this: <xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/"/> Notice that there is NO schemaLocation attribute. This is perfectly legal per the XML Schema specs (the schemaLocation attribute is rated #IMPLIED, iow optional, see http://www.w3.org/2001/XMLSchema.dtd). In other words, the code shouldn't even bother trying to look for anything. Instead, it tries to look for 'null'. Basically, it's probably something as simple as adding something like this to the code: if schemaLocation not equal null then resolve the import (whatever the code does now) else do nothing --- Michael Glavassevich <[EMAIL PROTECTED]> wrote: > footh <[EMAIL PROTECTED]> wrote on 03/16/2007 07:52:27 > PM: > > > Take this wsdl: > > > > > http://www.nws.noaa.gov/forecasts/xml/SOAP_server/ndfdXMLserver.php?wsdl > > > > Notice in the schema section there are two import > > statements with namespace attributes, but no > > schemaLocation attributes. This is perfectly > legal > > per the XML Schema spec. > > > > However, when using the XMLGrammarPreparser to > > preparse the schema, the following error is > generated > > twice (once for each import): > > > > schema_reference.4: Failed to read schema document > > 'null', because 1) could not find the document; 2) > the > > document could not be read; 3) the root element of > the > > document is not <xsd:schema>. > > Are you sure you're not just getting a warning > message? Xerces will report > one if it cannot locate [1] a schema document for an > import after: > > 1) querying its local cache; then > 2) querying the grammar pool if one was registered; > then > 3) querying the entity resolver if one was > registered; then > 4) dereferencing the schema location hint if one was > provided. > > If no schema document is found after all these > steps, it's *not* an error. > > > Presumably, the code is looking for the > schemaLocation > > attribute, not finding it and instead trying to > find > > 'null'. I'm thinking this could be a bug, but I > may > > be doing something wrong. Can anyone offer any > input > > or suggestions? > > The message just isn't very informative. This isn't > a bug, but it > certainly could be improved. > > If you want these imports to resolve you should > register an entity > resolver which locates a schema document based on > the target namespace > (and possibly other information provided in the > XMLSchemaDescription). > > > Thanks, > > > > JBF > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > [1] > http://www.w3.org/TR/xmlschema-1/#schema_reference > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: [EMAIL PROTECTED] > E-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > ____________________________________________________________________________________ We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. http://tv.yahoo.com/collections/265 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
