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 58322 - Exception thrown while automatic synchronization
Summary: Exception thrown while automatic synchronization
Status: CLOSED INVALID
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Daniel Prusa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-26 11:12 UTC by Jiri Prox
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Prox 2005-04-26 11:12:06 UTC
NB 4.1 (200504241930)
JDK 1.5.0_03

The exception is thrown when performing automatic source synchronization in
"without confirmation" mode.

Steps:
1) Switch on the automatic synchronization in Tools | Options | Source
Synchronization | Synchronization Enabled
2) Create new interface and new class implementing it
3) in dialog choose "Perform synchronization without confirmation"
4) Process
5) Change interface

Result: the exception in thrown

Annotation: Exception occurred in Request Processor
java.lang.NullPointerException
	at
org.netbeans.modules.java.codesync.ClassDependencyImpl.getJMIElement(ClassDependencyImpl.java:562)
	at
org.netbeans.modules.java.codesync.ClassDependencyImpl$Synchronizer.run(ClassDependencyImpl.java:211)
	at org.openide.util.Task.run(Task.java:189)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:330)
[catch] at
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:721)
Comment 1 Jiri Prox 2005-04-26 11:24:16 UTC
It is the same with Tools | Options | Source
Synchronization | Synchronization Enabled switched to ON
Comment 2 Martin Matula 2005-04-26 14:48:36 UTC
Dan please look at it.
Comment 3 Jan Becicka 2005-08-22 15:55:47 UTC
Tools->Synchronize was removed. This bug is not valid any more.
Comment 4 Jiri Prox 2006-03-22 10:35:24 UTC
verified