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 129531 - DTD node action: Action failed due to internal error
Summary: DTD node action: Action failed due to internal error
Status: RESOLVED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Sonali Kochar
URL:
Keywords:
: 130372 143487 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-03-07 11:38 UTC by tonybeckham
Modified: 2008-08-11 16:21 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Error message in console (7.22 KB, text/plain)
2008-03-07 12:47 UTC, tonybeckham
Details
error plain text (6.83 KB, text/plain)
2008-03-07 13:57 UTC, tonybeckham
Details
Log file for fix failed (48.72 KB, text/plain)
2008-06-04 18:54 UTC, tonybeckham
Details
Fix Failed thread dump (18.86 KB, text/plain)
2008-06-04 18:54 UTC, tonybeckham
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tonybeckham 2008-03-07 11:38:25 UTC
The DTD node action SAX Document Handler Wizard gives error message "Action failed due to internal error!" if the DTD
file is located in any folder besides src.

Steps:
1. Create a java application
(create the following in another location besides src)
2. create purchase order sample
3. from this generate sample xml
4. from the xml file generate DTD
5. On the dtd try the action SAX Document Handler Wizard
6. When you try and finish the wizard the error is shown.

System Info:
Product Version: NetBeans IDE Dev (Build 200803051205)
Java: 1.5.0_13; Java HotSpot(TM) Client VM 1.5.0_13-119
System: Mac OS X version 10.5.2 running on i386; MacRoman; en_US (nb)
Comment 1 tonybeckham 2008-03-07 12:47:55 UTC
Created attachment 57973 [details]
Error message in console
Comment 2 tonybeckham 2008-03-07 13:57:16 UTC
Created attachment 57980 [details]
error plain text
Comment 3 Sonali Kochar 2008-03-07 16:41:57 UTC
When you say a location other than src, do you mean test packages?
Comment 4 tonybeckham 2008-03-07 17:11:07 UTC
For a java project, if the dtd file is in any package other than default package this happens.  For a BPEL project is is
simple to see because all files must be in the project files folder.
Comment 5 Sonali Kochar 2008-03-07 21:20:00 UTC
Fixed.. I somehow didnt get the mercury notification.
Here's the output of hg out
changeset:   72021:123e0f8e1291
user:        Sonali Kochar <sonali@netbeans.org>
date:        Fri Mar 07 10:12:54 2008 -0800
summary:     Fix for http://www.netbeans.org/issues/show_bug.cgi?id=129531
Comment 6 tonybeckham 2008-05-22 19:38:06 UTC
Fix failed (or was not actually integrated that is why no mercurial notification)
Comment 7 Samaresh Panda 2008-05-30 18:29:28 UTC
Fixed: http://hg.netbeans.org/main/rev/a5ccc901576e
Comment 8 tonybeckham 2008-06-03 18:31:08 UTC
This fixes the problem for DTD located in package other than src for java projects, but same error still exists for BPEL
projects.

System Info:
Product Version: NetBeans IDE Dev (Build 200806030004)
Java: 1.6.0_05; Java HotSpot(TM) 64-Bit Server VM 1.6.0_05-b13-52
System: Mac OS X version 10.5.3 running on x86_64; MacRoman; en_US (nb)
Comment 9 Samaresh Panda 2008-06-03 20:00:47 UTC
Fixed: http://hg.netbeans.org/main/rev/5d7ca3b00a53
Comment 10 tonybeckham 2008-06-04 18:53:34 UTC
Fix Failed.  There is no exception in the IDE but the IDE becomes hung.  Attaching log and thread dump.

Product Version: NetBeans IDE Dev (Build 200806040005)
Java: 1.6.0_05; Java HotSpot(TM) 64-Bit Server VM 1.6.0_05-b13-52
System: Mac OS X version 10.5.3 running on x86_64; MacRoman; en_US (nb)
Comment 11 tonybeckham 2008-06-04 18:54:09 UTC
Created attachment 62382 [details]
Log file for fix failed
Comment 12 tonybeckham 2008-06-04 18:54:33 UTC
Created attachment 62383 [details]
Fix Failed thread dump
Comment 13 Samaresh Panda 2008-06-05 15:40:31 UTC
Interesting...Can you provide me some more info like what exactly you were trying to do when it occurred?
Comment 14 tonybeckham 2008-06-05 18:01:12 UTC
Create New BPEL Module project
Add Purchase Order Schema
Generate Sample XML w/ PurchaseOrder as root element
From the XML document generate DTD
For the DTD use the SAX Document handler Wizard accept all defaults
When finishing the wizard this happens.

On other platforms still get same Action Failed message but IDE still becomes hung at that point.
Comment 15 tonybeckham 2008-06-05 18:20:02 UTC
With new build (Build 200806050006) hang is not happening but problem persists.
Comment 16 Samaresh Panda 2008-06-06 22:20:27 UTC
For me, it generates all classes, however, I see that the generation is not perfect. I do not get any errors and no hang.
Comment 17 tonybeckham 2008-06-09 21:38:17 UTC
On Mac OS there is no exception thrown in the IDE, only in the log but the SAXBindings.xml file is not generated.

On Linux the exception is thrown in the IDE, but similarly, the SAXBindings.xml file is not generated.


Last tested on Build 080609
Comment 18 Samaresh Panda 2008-06-11 00:30:03 UTC
This has something to do with a bpel project. If you try the same in a java app or web app, it works fine. Note that the
code generation requires class-path and package information. Sounds like bpel projects have no such notion. I realized
that I cannot even create a package in bpel module. That tells me that it is specific to bpel and hence I have to lower
the priority.
Comment 19 Samaresh Panda 2008-06-11 16:19:22 UTC
I realized, user cannot create a java class inside a bpel project. So I think we should track this as a separate issue
(a task rather) that should not allow any form of java code generation in any non-java projects. 
Comment 20 Samaresh Panda 2008-06-25 20:20:19 UTC
*** Issue 130372 has been marked as a duplicate of this issue. ***
Comment 21 tonybeckham 2008-07-08 19:44:32 UTC
Have you filed an issue about java classes in BPEL project?  I think that the option for SAX Document Handler Wizard
should be removed from the context menu for BPEL projects.  Otherwise, I think this issue will be reported over and over
by users.
Comment 22 Sonali Kochar 2008-07-22 17:54:21 UTC
Filed issue:
http://www.netbeans.org/issues/show_bug.cgi?id=141207

Marking this issue as fixed
Comment 23 tonybeckham 2008-07-22 18:33:19 UTC
So, will the option for SAX Document Handler Wizard be removed from the context menu for BPEL projects?
Comment 24 Samaresh Panda 2008-08-11 16:21:57 UTC
*** Issue 143487 has been marked as a duplicate of this issue. ***