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.
Note: I was in a much more complex situation when a similar Exception happened which corrupted my WSDL document. This is the simplest way I know to reproduce the problem, although it is really too hard for me to detail the steps to reproduce the complex situation I've encountered. But please take a look at this Exception because it may be related to the WSDL document corruption problem which I've encountered. -------------------------- How to reproduce: 1. create a New Project -> SOA -> BPEL, choose default for everything but set Binding Type to JMS 2. create a new WSDL Document under "Process Files" in the newly created BPEL module 3. In WSDL document, delete everything under Services 4. Now add Service under "Services", then add Service Port under the newly created service 5. Add JMS Address under the newly created service port 6. Delete the service port and click on "Refactor" 7. Hopefully you will see the Exception and stack trace Also see http://statistics.netbeans.org/exceptions/detail.do?id=3174 It may give you more background information to the bug itself.
I have not been able to reproduce this issue.
Verified that I cannot reproduce this stack trace with Product Version: NetBeans IDE Dev (Build 200710290000) Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05 System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb) Userdir: C:\Documents and Settings\lautz\.netbeans\dev Reopen if you can provide more info.