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.
Using a local build from 9/29/06, a NPE exception was thrown when I launched the IDE. The IDE never came up after that. With 10/2/06 local build, I was not able to replicate the issue. However, with 10/3/06 local build, the same exception was thrown again but only after IDE launched successfully. So this time the IDE did come up and didn't see anything offhand that might have been affected by the NPE though. java.lang.NullPointerException at org.netbeans.modules.bpel.debugger.ui.util.ModelUtil$2MyRunnable.run (ModelUtil.java:105) at org.netbeans.modules.bpel.model.impl.BpelModelImpl.invoke (BpelModelImpl.java:248) at org.netbeans.modules.bpel.debugger.ui.util.ModelUtil.getBpelEntityId (ModelUtil.java:113) at org.netbeans.modules.bpel.debugger.ui.editor.BpelEditorContext.annotate (BpelEditorContext.java:97) at org.netbeans.modules.bpel.debugger.api.EditorContextBridge.annotate (EditorContextBridge.java:160) at org.netbeans.modules.bpel.debugger.ui.breakpoint.BpelBreakpointListener.annotat e(BpelBreakpointListener.java:126) at org.netbeans.modules.bpel.debugger.ui.breakpoint.BpelBreakpointListener.breakpo intAdded(BpelBreakpointListener.java:60) at org.netbeans.api.debugger.DebuggerManager.fireBreakpointCreated (DebuggerManager.java:638) at org.netbeans.api.debugger.DebuggerManager.initBreakpoints (DebuggerManager.java:728) at org.netbeans.api.debugger.DebuggerManager.getBreakpoints (DebuggerManager.java:462) at org.netbeans.modules.debugger.projects.BreakpointAnnotationProvider.annotate (BreakpointAnnotationProvider.java:43) at org.openide.text.CloneableEditorSupport.ensureAnnotationsLoaded (CloneableEditorSupport.java:339) at org.openide.text.CloneableEditor.initialize (CloneableEditor.java:268) at org.openide.text.CloneableEditor.getEditorPane (CloneableEditor.java:635) at org.netbeans.core.multiview.MultiViewCloneableTopComponent.getEditorPane (MultiViewCloneableTopComponent.java:231) at org.openide.text.CloneableEditorSupport.getOpenedPanes (CloneableEditorSupport.java:856) at org.netbeans.modules.debugger.projects.EditorContextImpl.getCurrentEditor (EditorContextImpl.java:581) at org.netbeans.modules.debugger.projects.EditorContextImpl.getCurrentLineNumber (EditorContextImpl.java:241) at org.netbeans.modules.debugger.projects.RunToCursorActionProvider.shouldBeEnable d(RunToCursorActionProvider.java:149) at org.netbeans.modules.debugger.projects.RunToCursorActionProvider.access$100 (RunToCursorActionProvider.java:64) at org.netbeans.modules.debugger.projects.RunToCursorActionProvider$Listener.prope rtyChange(RunToCursorActionProvider.java:196) at java.beans.PropertyChangeSupport.firePropertyChange (PropertyChangeSupport.java:333) at java.beans.PropertyChangeSupport.firePropertyChange (PropertyChangeSupport.java:270) at org.netbeans.core.windows.RegistryImpl.doFirePropertyChange (RegistryImpl.java:255) at org.netbeans.core.windows.RegistryImpl.tryFireChanges (RegistryImpl.java:228) at org.netbeans.core.windows.RegistryImpl.selectedNodesChanged (RegistryImpl.java:192) at org.netbeans.core.windows.RegistryImpl.topComponentActivated (RegistryImpl.java:144) at org.netbeans.core.windows.WindowManagerImpl.notifyRegistryTopComponentActivated (WindowManagerImpl.java:919) at org.netbeans.core.windows.Central.setActiveMode (Central.java:188) at org.netbeans.core.windows.WindowManagerImpl.setActiveMode (WindowManagerImpl.java:617) at org.netbeans.core.windows.PersistenceHandler.load (PersistenceHandler.java:184) at org.netbeans.core.windows.WindowSystemImpl.load (WindowSystemImpl.java:45) at org.netbeans.core.NonGui$3.run(NonGui.java:224) at java.awt.event.InvocationEvent.dispatch (InvocationEvent.java:209) at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
Actually the NPE exception was thrown when I selected an Assign activity and it looks like the trace log is somewhat similar but not exactly the same as the trace above.
Created attachment 34875 [details] npe exception generated after selecting Assign activity
please see attached for the new generated NPE exception.
please be on the alert for problems related to breakpoint persistence. Breakpoints are persisted in the userdir. So there is a valid use case where we need to be testing the proper persistence and restoration of breakpoint information. Maybe QE needs to do more testing in this area.
I can not reproduce the bug in build 061003 on Linux and Windows.
As I can not think of any situation in which the described bug can be reproduced, there is really a typo in the following code that may lead to the specified exception: FindHelperImpl.java line 104 : return ret.toArray( new BpelEntity[ list.size()] ); supposed to be return ret.toArray( new BpelEntity[ ret.size()] );
Please provide an information about using of pointed method in FindHelper. As I understand ( and this was discussed ) debugger invoke this method ONLY for existing BPEL entity ( the usecase of situation is : we know that xpath is pointer to some existed BPEL entity and we are trying to find this entity via xpath ). In this case pointed method will work fine without pointed correction. Difference could appear only when xpath point to not BPEL DOM element. Only in this case there will be a problem. So proposed fix will not fix THIS issue. The problem could appear either in XAM ( while delegating find method to XAM api ) or in incorrect using of method in FindHelper. Proposed correction for FindHelperImpl will be introduced in source code, but as I already said it doesn't concern to this issue.
OK, the XAM part of the problem is already fixed, so I believe we can close this issue.
The bug is not reproducible so I mark it as verified.