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 18409 - "Parse fatal error..." on EJB deployment descriptors
Summary: "Parse fatal error..." on EJB deployment descriptors
Status: CLOSED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Windows 3.1/NT
: P3 blocker (vote)
Assignee: issues@xml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-06 13:07 UTC by ats37
Modified: 2003-07-02 08:37 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 ats37 2001-12-06 13:07:34 UTC
Using the XML modules I just downloaded from the beta update center 
(200111301106 build), if I try and open a tree (or expand it in the explorer 
window) for my existing EJB deployment descriptors, I just get a "Parse fatal 
error..." message.  However, if use the Check XML/Validate XML menu options on 
them, there are no errors displayed (and they deploy okay, so I believe they're 
correct).

The problem appears to be to do with the
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 
1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd">
line - this is identical to the example in the EJB 1.1 spec.  Likewise, the EJB 
2.0 spec says
'All valid ejb-jar deployment descriptors must contain the following DOCTYPE 
declaration:
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">'

If I create a new xml file named ejb-jar using the "XML with DTD" template, 
open it up in tree view and change the public ID on the main node to either of 
the above (or any of the separate strings, with or without quotes), I get 
an "Invalid public ID" warning dialog, and it reverts to <DEFAULT>.  Whether or 
not it really is invalid, I wouldn't know.  However, since there's likely to be 
a lot of files with these DOCTYPE declarations, I think the XML module ought to 
be able to handle them.
Comment 1 _ lkramolis 2001-12-06 14:46:36 UTC
I am so sorry for that, this was wrong implementation of PublicId
check. It is already fixed and will be in next beta release, which
will be at the end of next week.
Comment 2 Martin Schovanek 2002-01-10 12:49:10 UTC
VERIFIED
Comment 3 Quality Engineering 2003-07-02 08:37:57 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.