You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by Lawrence Mandel <lm...@ca.ibm.com> on 2006/01/18 20:40:46 UTC
Should WSDL522 be a warning?
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
lmandel@ca.ibm.com
Re: Should WSDL522 be a warning?
Posted by Arthur Ryman <ry...@ca.ibm.com>.
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: 4169395063@fido.ca
Lawrence Mandel/Toronto/IBM@IBMCA
01/18/2006 02:40 PM
Please respond to
woden-dev
To
woden-dev@ws.apache.org
cc
Subject
Should WSDL522 be a warning?
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
lmandel@ca.ibm.com
Re: Should WSDL522 be a warning?
Posted by Lawrence Mandel <lm...@ca.ibm.com>.
+1 to your suggestion to move both 521 and 522 to warnings.
Lawrence Mandel
Software Developer
IBM Rational Software
Phone: 905 - 413 - 3814 Fax: 905 - 413 - 4920
lmandel@ca.ibm.com
John Kaputin <KA...@uk.ibm.com>
01/19/2006 11:05 AM
Please respond to
woden-dev
To
woden-dev@ws.apache.org
cc
Subject
Re: Should WSDL522 be a warning?
Hi Lawrence,
with this specific test case failure that reports the WSDL522 woden
message
in the parseSchemaImport method, we know it's because of a bug in
XmlSchema
(incorrect context used for relative paths specified in the
'schemaLocation' attribute of nested xs:imports).
In the more general case of an XmlSchemaException (which triggers the
WSDL522 message), I guess we should just consider this a schema
dereferencing problem but not necessarily an error, unless we later fail
to
dereference a QName from that schema (i.e. it's a QName dereference
problem
that's an error, not the initial failure to dereference a schemaLocation).
So I will change this use of WSDL522 to severity 'Warning' rather than
'Error', as you suggest.
What about the use of WSDL521 in parseSchemaInline, which is also reported
as an error? Once again we start with the DOM element for the top level
(inlined) schema and an XmlSchemaException is caught, but we cannot tell
whether it is a problem parsing the inlined schema components or
dereferencing an xs:import nested within the inlined schema. Unless there
are any objections, I will treat this the same as WSDL522 (i.e. Warning) -
an error only occurs if we later attempt to dereference a QName from that
schema.
John Kaputin
Lawrence Mandel
<lmandel@ca.ibm.c
om> To
woden-dev@ws.apache.org
18/01/2006 19:40 cc
Subject
Please respond to Should WSDL522 be a warning?
woden-dev
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
lmandel@ca.ibm.com
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Should WSDL522 be a warning?
Posted by John Kaputin <KA...@uk.ibm.com>.
Hi Lawrence,
with this specific test case failure that reports the WSDL522 woden message
in the parseSchemaImport method, we know it's because of a bug in XmlSchema
(incorrect context used for relative paths specified in the
'schemaLocation' attribute of nested xs:imports).
In the more general case of an XmlSchemaException (which triggers the
WSDL522 message), I guess we should just consider this a schema
dereferencing problem but not necessarily an error, unless we later fail to
dereference a QName from that schema (i.e. it's a QName dereference problem
that's an error, not the initial failure to dereference a schemaLocation).
So I will change this use of WSDL522 to severity 'Warning' rather than
'Error', as you suggest.
What about the use of WSDL521 in parseSchemaInline, which is also reported
as an error? Once again we start with the DOM element for the top level
(inlined) schema and an XmlSchemaException is caught, but we cannot tell
whether it is a problem parsing the inlined schema components or
dereferencing an xs:import nested within the inlined schema. Unless there
are any objections, I will treat this the same as WSDL522 (i.e. Warning) -
an error only occurs if we later attempt to dereference a QName from that
schema.
John Kaputin
Lawrence Mandel
<lmandel@ca.ibm.c
om> To
woden-dev@ws.apache.org
18/01/2006 19:40 cc
Subject
Please respond to Should WSDL522 be a warning?
woden-dev
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
lmandel@ca.ibm.com
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org