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 47717 - Validation of context.xml
Summary: Validation of context.xml
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P4 blocker (vote)
Assignee: Milan Kuchtiak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-23 15:42 UTC by Geertjan Wielenga
Modified: 2005-01-13 08:13 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 Geertjan Wielenga 2004-08-23 15:42:45 UTC
Validation of context.xml results in cryptic message:

XML validation started.

Checking
file:/C:/MyWebApp/HelloWeb/web/META-INF/context.xml...
cvc-elt.1: Cannot find the declaration of element
'Context'. [1]
XML validation finished. 

Because context.xml has no DTD or Schema,
validation should be disabled or the message
should be clearer.
Comment 1 Martin Schovanek 2004-08-23 16:48:53 UTC
It is message from validator which try to say: there is no DTD or
Schema for this document (root element). IMHO the action should be
disabled because a DTD or Schema for context.xml doesn't exist.
Comment 2 Milan Kuchtiak 2004-09-20 10:37:19 UTC
There is no option in jeeserver to enable/disable the XML validation
for the ConfigDataObject. The XML validation is always enabled in
ConfigDO.
The message comes from XML parser.

Actually I don't know what to do with the bug. However, I don't think
it is critical. 
It is the same for all XML documents where DTD or schema is missing.
Comment 3 Geertjan Wielenga 2004-09-21 10:53:42 UTC
So, if this means the message can't be changed and if this means XML
validation can't be disabled, there doesn't seem to be any solution
and the issue should be closed?
Comment 4 Geertjan Wielenga 2004-11-15 10:55:26 UTC
Milan, should this issue be closed?
Comment 5 Milan Kuchtiak 2004-11-15 12:59:28 UTC
I think so. Actually, there is no solution for this issue.
Comment 6 Geertjan Wielenga 2005-01-13 08:13:44 UTC
No solution for this issue.