Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » Known bugs with XML/XSD editing and xs:include usage?
Known bugs with XML/XSD editing and xs:include usage? [message #657356] Wed, 02 March 2011 14:37 Go to next message
Stuart Rossiter is currently offline Stuart Rossiter
Messages: 4
Registered: March 2011
Junior Member
Using the latest Helios build, I still have what appears to be obvious bugs/unsupported features related to use of xs:include entries for XML and XML Schema editing.

(i) If including another schema, content assistance does not 'see' types in the included schema, so any such types have to be entered manually

(ii) When creating an XML file based on an XML schema, there is a similar problem: included schemas within the main schema file are not used and you get a semi-empty XML document

Are either of these known bugs (I did a search and couldn't find anything)?? If no-one is aware that they are, I will raise something on Bugzilla.

Cheers,
Stuart
Re: Known bugs with XML/XSD editing and xs:include usage? [message #657367 is a reply to message #657356] Wed, 02 March 2011 15:04 Go to previous messageGo to next message
Stuart Rossiter is currently offline Stuart Rossiter
Messages: 4
Registered: March 2011
Junior Member
Oops, my error.

The problem is when using relative paths as the schemalocation. My understanding is that this is not officially part of the XML Schema standard (since relative paths are not URIs) but that some/many(?) parsers support it (and IDEs such as Visual Studio support it).

Is this supposed to work with WTP or not? Is my understanding above correct?

Thanks,
Stuart
Re: Known bugs with XML/XSD editing and xs:include usage? [message #657370 is a reply to message #657356] Wed, 02 March 2011 15:15 Go to previous messageGo to next message
Stuart Rossiter is currently offline Stuart Rossiter
Messages: 4
Registered: March 2011
Junior Member
OK , I did a little more digging. Looks like it might be a consequence of this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=196353

The included schema are in a different Eclipse project, which squares with this bug.

I can work around it with absolute file: URIs, but not ideal Sad
Re: Known bugs with XML/XSD editing and xs:include usage? [message #657406 is a reply to message #657367] Wed, 02 March 2011 16:59 Go to previous messageGo to next message
Ed Merks is currently offline Ed Merks
Messages: 26138
Registered: July 2009
Senior Member
Stuart,

Relative URIs are still well defined URIs according to the RFC for
URIs. Such things are used heavily in HTML after all, and are
definitely supported by XML Schema or any other XML document. The
important thing to keep in mind is "what URI is used to address the
document containing the relative URI" because the relative URI will be
resolved to an absolute URI based on that. So if the schema resource is
opened with URI platform:/resource/<project>/<path>/My.xsd (what I'd
expect) then you could expect a relative path
.../../<other-project>/<other-path>/Other.xsd to resolve to URI
platform:/resource/<other-project>/<other-path>/Other.xsd. (Note that
"\" is not a segment separator in a URI.)


Stuart Rossiter wrote:
> Oops, my error.
>
> The problem is when using relative paths as the schemalocation. My
> understanding is that this is not officially part of the XML Schema
> standard (since relative paths are not URIs) but that some/many(?)
> parsers support it (and IDEs such as Visual Studio support it).
>
> Is this supposed to work with WTP or not? Is my understanding above
> correct?
>
> Thanks,
> Stuart
>
Re: Known bugs with XML/XSD editing and xs:include usage? [message #657415 is a reply to message #657406] Wed, 02 March 2011 17:35 Go to previous message
Stuart Rossiter is currently offline Stuart Rossiter
Messages: 4
Registered: March 2011
Junior Member
Thanks Ed: good description.

I actually worked this out in the meantime whilst browsing the bug I quoted and trying some things. See my comments there because the bug appears to be fixed: or at least if I apply 'platform URI thinking' Smile as you discuss, the relative URIs resolve, despite being across projects and to real file locations outside of the Eclipse workspace directory (which the bug suggested was failing).

https://bugs.eclipse.org/bugs/show_bug.cgi?id=196353
Previous Topic:IWAB0506E Error
Next Topic:Web Page Editor's palette withot JSF groups
Goto Forum:
  


Current Time: Fri Oct 24 12:17:18 GMT 2014

Powered by FUDForum. Page generated in 0.02811 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software