| WSDL Parser error [message #222581] |
Mon, 06 October 2008 10:45  |
Eclipse User |
|
|
|
Hello all,
I have a WSDL file with some inline schemas lets name them A and B.
the schema A refers to some components in schema B and it doesnt have any
import statement for B. This is a valid WSDL as per the specification and
i dont get any errors when i validate this with Altova XML spy and some
more validators.
The validator in eclipse shows this as an invalid schema.
But when i get the model for this WSDL using WSDLResourceImpl and then
check the schemas the components are resolved and i can see the components
of schema B getting resolved in schema A. but when i call validate on the
EMF models of the schema it gives me the validation errors that the
components
cannot be resolved.
Thanks and regards,
Keshav Veerapaneni.
|
|
|
|
|
|
|
|
| Re: WSDL Parser error [message #222759 is a reply to message #222631] |
Mon, 20 October 2008 06:12  |
| Eclipse User |
|
|
|
This is a multi-part message in MIME format.
--------------010701060609070900070602
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Keshavrao,
Sorry, I didn't have much time for newsgroups last week. What you're
quoting below is the part of the specification that says <xsd:import/>
is valid because schemaLocation is an optional hint and the because
namespace can be null. So <xsd:import> is used to import components
from the null target namespace without specifying where to find the
schema for that. It in no way implies that the import isn't necessary.
In fact, if you think about it, if an import isn't necessary in the
first place, then <xsd:import> would be pointless. In fact, it's
*required *if you want to reference names from the null namespace.
I would never trust XML Spy's lack of an error message as a good
indicator of validity. The only other arbiter I trust is Xerces and
I've discussed the interpretation of the specification as it relates to
this specific issue with Xerces' developers...
Keshavrao wrote:
> Hello Ed,
>
> Thanks for the quick reply.
>
> I found the below line in the XSD 1.1 specification which actually
> does'nt put any restriction on what basis the components are to be
> resolved.
>
> <B>
> Note: Since both the namespace and schemaLocation [attribute] are
> optional, a bare <import/> information item is allowed. This simply
> allows unqualified reference to foreign components with no target
> namespace without giving any hints as to where to find them.
> </B>
>
> Should we not consider WSDL specification to be driving here? as it is
> part of WSDL specification that allows to have multiple inline schemas
> and here the WSDL spec should know how to resolve the components
> within these inline schemas.
>
> Also the parser is actually able to resolve the components and the
> only problem that comes is when i explicitly call validate on the XSD.
>
> Thanks and regards,
> Keshav Veerapaneni.
>
--------------010701060609070900070602
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Keshavrao,<br>
<br>
Sorry, I didn't have much time for newsgroups last week.
|
|
|
|
| Re: WSDL Parser error [message #222872 is a reply to message #222759] |
Tue, 21 October 2008 02:04 |
| Eclipse User |
|
|
|
Hello Ed,Dave,
Thanks for the information. I will also report this Altova XML Spy and
will try describing the issue and check why is this allowed.
Thanks for the support again.
Regards,
Keshav Veerapaneni.
|
|
|
Powered by
FUDForum. Page generated in 2.28989 seconds
Home