I agree that <import> statements should only cause warnings if the schemalocation is bad. It's technically only a hint. However, failure to import MAY resoult in a downstream QName resolution error.
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]
| Lawrence Mandel/Toronto/[EMAIL PROTECTED]
01/18/2006 02:40 PM
|
|
Hi John,
I was taking a look at some of the schema errors and warnings you've defined to sort out some JUnit failures and came across one I think should be a warning.
WSDL522=Could not parse a schema imported from URL "{0}".
This error indicates that a schema model could not be created because the schema could not be parsed. I think this should be a warning as any imported schemas that cannot be located or read should produce warnings but not cause errors as other schema import statements may import the same namespace and still allow the WSDL document to be valid.
Comments?
Lawrence Mandel
Software Developer
IBM Rational Software
Phone: 905 - 413 - 3814 Fax: 905 - 413 - 4920
[EMAIL PROTECTED]
