|
|
|
Re: WSDL Parser error [message #222636 is a reply to message #222631] |
Mon, 13 October 2008 13:29 |
Eclipse User |
|
|
|
Originally posted by: dcarver.starstandard.org
What does the XSD 1.0 specification say, as there are differences
between the official XSD 1.0 Recommendation and the Working draft of XSD
1.1.
Dave
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.
>
|
|
|
|
Re: WSDL Parser error [message #222698 is a reply to message #222640] |
Fri, 17 October 2008 15:20 |
Eclipse User |
|
|
|
Originally posted by: dcarver.starstandard.org
Keshavrao wrote:
> Hello Dave,
>
> Even the XSD1.0 says the same, both the namespace and location are
> optional and
> its upto the tools and implemention, how it makes the referred components
> resolvable.
>
Most tooling I know of is going to require at least a namespace on an
Import so that it can check it's cache of grammars or at least an XML
Catalog to see if it already has something it can reference.
|
|
|
Re: WSDL Parser error [message #222759 is a reply to message #222631] |
Mon, 20 October 2008 10:12 |
Ed Merks Messages: 33218 Registered: July 2009 |
Senior Member |
|
|
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.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04994 seconds