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 50385 - Failure when generating SAX handlers fromDTD
Summary: Failure when generating SAX handlers fromDTD
Status: RESOLVED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Milan Kuchtiak
URL:
Keywords: UI
Depends on:
Blocks:
 
Reported: 2004-10-13 19:01 UTC by ldunaway
Modified: 2005-11-18 20:04 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments
Stack trace (3.30 KB, text/plain)
2004-10-13 19:02 UTC, ldunaway
Details
The DTD (3.00 KB, text/plain)
2004-10-13 19:03 UTC, ldunaway
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ldunaway 2004-10-13 19:01:38 UTC
Action failed due to internal error! when
generating SAX handlers from DTD
Comment 1 ldunaway 2004-10-13 19:02:47 UTC
Created attachment 18275 [details]
Stack trace
Comment 2 ldunaway 2004-10-13 19:03:40 UTC
Created attachment 18276 [details]
The DTD
Comment 3 Milan Kuchtiak 2004-10-29 11:10:49 UTC
Yes, the SAX handlers generation is broken when DTD file isn't located
in a package.
If you put your dtd file to src/anypackage it should work.
Comment 4 _ rkubacki 2005-03-18 10:06:27 UTC
This is a problem in Java bridge.
Comment 5 Martin Matula 2005-03-18 10:19:33 UTC
Dan, please look at it.
Radime, or anyone, how can we reproduce this?
Comment 6 _ rkubacki 2005-03-18 10:23:55 UTC
Oops, there are two problems:
one pointed by original submitter - Java bridge fails to create handler. This
seems to be fixed in current dev builds
second that the action issues misleading error if the action is invoked on a
file that is not under some source root.

To fix the second problem we need to update the wizard (add possibilty to choose
target location of generated sources). I guess such UI change is not possible
for 4.1.
Comment 7 Jiri Kovalsky 2005-10-17 08:08:06 UTC
Can somebody please reevaluate this problem ?
Comment 8 Milan Kuchtiak 2005-11-18 20:04:20 UTC
The problem with exception was fixed.

There is still a minor issue :
User can create DocumentHandler class and other java artifacts outside a
package. In this case, in java project for example, generated classes will not
be part of deliverable jar file.
Nevertheless, that is not a big issue as there is a workaround : either copy the
classes or create a secondary source root.
I've created a separate issue for this : see the issue 68968.

I suggest also an entire re-design of generated DocumentHandler.
See the issue  68969.

I am marking this issue as fixed.