This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 22118 - XML Validation on CVS Mount fails
Summary: XML Validation on CVS Mount fails
Status: CLOSED WORKSFORME
Alias: None
Product: xml
Classification: Unclassified
Component: API (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: _ pkuzel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-05 00:58 UTC by Moazam A. Raja
Modified: 2007-09-25 01:29 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Moazam A. Raja 2002-04-05 00:58:51 UTC
XML documents with private DTD declarations (SYSTEM) 
pointing to relative paths will not validate from a CVS 
Mounted File System.


The error message is always that the DTD file cannot be 
found. After some poking around, I discovered that 
regardless of where in the CVS Mount the XML document 
exists, the "working directory" of the validation process 
seems to be the FFJ installation directory.


To Reproduce:


1. Mount a CVS directory
2. Somewhere a single folder on the tree place a XML 
document and a DTD
3. Ensure that the DOCTYPE for the XML document reads 
DOCTYPE rootelement SYSTEM "dtdfile.dtd" (A relative path 
to the DTD)
4. Right Click on the XML document and choose validate.
5. Error message should show that the DTD file was not 
found.


This seems to work fine when this is not in a CVS tree or 
you provide a fullly qualified URL to a PUBLIC DOCTYPE 
declaration.


Note: When looking for a relative DTD, forte is looking 
relative to the runide.exe executable, not to the XML 
document itself.
Comment 1 _ lkramolis 2002-04-05 06:46:21 UTC
Assigned to tools sub-module where Validate action is implemented.
Comment 2 _ pkuzel 2002-04-26 09:48:19 UTC
I tested it in latest 26/Apr/2002 NetBeans builds and it works well.

In Forte 3.0 you can workaround it by assigning public IDs to your
DTDs and register those public IDs in entity catalog. Then you
reference your DTD using the public ID.
Comment 3 Martin Schovanek 2002-10-09 15:15:32 UTC
VERIFIED
Comment 4 Quality Engineering 2003-07-02 08:41:33 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.