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 130372 - SAX Document Handler Wizard failed due to internal errors.
Summary: SAX Document Handler Wizard failed due to internal errors.
Status: RESOLVED DUPLICATE of bug 129531
Alias: None
Product: xml
Classification: Unclassified
Component: Tools (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Samaresh Panda
URL:
Keywords:
Depends on: 90174
Blocks:
  Show dependency tree
 
Reported: 2008-03-18 10:40 UTC by Keiichi Oono
Modified: 2008-06-25 20:20 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
IDE log file when wizard was failed (72.39 KB, text/plain)
2008-03-18 10:41 UTC, Keiichi Oono
Details
DTD file when I was testing (204 bytes, text/plain)
2008-03-18 10:43 UTC, Keiichi Oono
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Keiichi Oono 2008-03-18 10:40:12 UTC
6.1 Beta (Build 200803050202)

to reproduce:
  1. Create DTD (I've used attached simpletest.dtd)
  2. Start SAX Document Handler Wizard
       JAXP 1.1
       SAX  2.0
         all others are default
  3. When click "Finish" dialog box is displayed and it says:
      "Action failed due to internal error!"

Customized Bindings (*SAXBindings.xml) is not saved, and generated handler implementation (*HandlerImpl.java) is empty.
In the 5.5.1 release, the debugging code is inserted when de-selecting "Propagate SAX Events to Generated Handler".
Comment 1 Keiichi Oono 2008-03-18 10:41:21 UTC
Created attachment 58550 [details]
IDE log file when wizard was failed
Comment 2 Keiichi Oono 2008-03-18 10:43:11 UTC
Created attachment 58551 [details]
DTD file when I was testing
Comment 3 tonybeckham 2008-03-25 17:44:23 UTC
What type of project are you trying this in.  When I try a BPEL module I get the error, but in a java project I do not
when using the simpletest.dtd file.  Actually, for the java project scenario, the dtd has to be located in <default
package> to work, any other package returns same error.

A strange note, once task is completed in a java project, it can be completed anywhere, such as in a BPEL project, or
from the files view at any local location...
Comment 4 tonybeckham 2008-03-25 18:07:36 UTC
We should probably have a release note for the workaround if this will not get fixed for FCS.
Comment 5 Keiichi Oono 2008-03-28 09:51:23 UTC
Thank you for your reproducing and information. I"m using java project. And as you mentioned, I've confirmed that this
wizard works without any errors when DTD is located in default package.

Yes, it's good to write down the workaround in the release note if this can not be fixed by the release.
Comment 6 Samaresh Panda 2008-06-25 20:20:27 UTC
Has been fixed already.

*** This issue has been marked as a duplicate of 129531 ***