Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 343268

Summary: Relative DTD Paths are not resolved if they refer to a dtd file outside of the current project
Product: [WebTools] WTP Source Editing Reporter: Aysegul Aydin <ayzegul>
Component: wst.xmlAssignee: wst.xml <wst.xml-inbox>
Status: NEW --- QA Contact: Nick Sandonato <nsand.dev>
Severity: normal    
Priority: P3 CC: zalapa
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Aysegul Aydin CLA 2011-04-19 09:58:26 EDT
Build Identifier: 20110301-1815

We use relative dtd paths in our xml files. Before we upgrade to Eclipse Helios we could refer to dtd files that reside in other projects than the xml file referring to them. Suppose we have 2 projects A and B that are rooted in the same folder. We have a dtd file in project A and an XML file in project B uses that dtd. Xml file refers to this dtd as:


<!DOCTYPE database SYSTEM "../../A/somefolder/someDtdFile.dtd" >

Before Eclipse Helios, XML editor was resolving this relative path correctly. But in Helios release, XML editor only resolves relative paths that reside in the same project as xml file. If we move the dtd file to project B, relative path works fine. We assume that in Eclipse Helios release, relative paths that reside out of the current project is intentionally ignored. We need a solution to this problem. Maybe a preference option that will be set to enable using relative paths outside the current project may be added. We could not find any workaround to this issue.


Reproducible: Always

Steps to Reproduce:
1. Create two projects in a workspace.
2. Create a dtd file in one project
3. Create an XML file in the other project that refers relatively (not absolute file path, since these xml files are on SVN and absolute paths differ from developer to developer.) to this dtd file such as "../../OtherProject/SomeFile.dtd"
4. You will get a warning message such as "The system cannot find the path specified"
Comment 1 Salvador Zalapa CLA 2013-07-08 16:41:04 EDT
This is working properly in Kepler, the path is being resolved when it refer to a dtd file from another project. This bug should be resolved.