This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 250838 - Allow VEX to work with Schemas as well as DTD
Summary: Allow VEX to work with Schemas as well as DTD
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: 1.0.0 M8   Edit
Assignee: Florian Thienel CLA
QA Contact: David Carver CLA
URL:
Whiteboard:
Keywords:
Depends on: 253753
Blocks:
  Show dependency tree
 
Reported: 2008-10-14 15:34 EDT by David Carver CLA
Modified: 2011-12-30 14:05 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Carver CLA 2008-10-14 15:34:23 EDT
Currently VEX only works with DTDs...it should be able to work with Schemas as well as those provided in the WTP XML Catalog.
Comment 1 David Carver CLA 2008-10-30 18:29:51 EDT
This is partially implemented by solving bug 250828.   The content model will load either a DTD or an XML Schema.
Comment 2 David Carver CLA 2010-07-08 11:28:35 EDT
This should also be able to use the XML Catalogs from WTP to resolve schemas.
Comment 3 David Carver CLA 2010-07-19 09:49:23 EDT
Just realized that this bug will also depend ong bug 253753 (Namespace support) being added to the VEX Model.  I've added bug 253753 as a dependency on this particular bug in order for it to be implemented.
Comment 4 Florian Thienel CLA 2011-05-23 15:41:53 EDT
Implementation hint: The WST URIResolver also accepts a namespace name as value for the publicId parameter.
Comment 5 Florian Thienel CLA 2011-11-09 17:35:45 EST
Moved to Mylyn Docs Vex.
Comment 6 Florian Thienel CLA 2011-12-30 14:05:13 EST
Basic implementation finished, the project plan can be loaded, edited and saved. All further features regarding XML schema should be specified in their own bug.