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 77313 - when removing glassfish from netbeans, triad of exceptions is thrown
Summary: when removing glassfish from netbeans, triad of exceptions is thrown
Status: RESOLVED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: EJB Project (show other bugs)
Version: 5.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Andrei Badea
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-02 14:37 UTC by Bernard Halas
Modified: 2006-09-11 21:03 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
stacktrace (27.56 KB, text/plain)
2006-06-02 14:39 UTC, Bernard Halas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bernard Halas 2006-06-02 14:37:32 UTC
NB 5.5 dev 200606020200
JDK 1.6.0 b85

Description:
============
after removing glassfish from netbeans a trio of exceptions is thrown
(InvocationTargetException, and 2x ArrayIndexOutOfBoundsException)

Steps to reproduce:
===================
1) register glassfish into NB
2) create new "EJB project" from category "Enterprise"
3) delete the newly created project also with sources
4) from the view runtime try to remove glassfish

That's it.
Comment 1 Bernard Halas 2006-06-02 14:39:41 UTC
Created attachment 30750 [details]
stacktrace
Comment 2 Petr Jiricka 2006-09-06 18:15:50 UTC
Hi Bernard, we did a lot of changes in this area, can you please try whether
this is still reproducible with the latest NetBeans 5.5 daily build and with the
latest JDK 6 build? Thanks.
Comment 3 Petr Jiricka 2006-09-06 18:24:02 UTC
I can still reproduce in the latest 5.5 build, here is the latest root cause
exception:

Caused by: java.lang.NullPointerException
	at
org.netbeans.modules.j2ee.ejbjarproject.EjbJarProvider.getEjbJar(EjbJarProvider.java:220)
	at
org.netbeans.modules.j2ee.ejbjarproject.EjbJarProvider.getDeploymentDescriptor(EjbJarProvider.java:202)
	at
org.netbeans.modules.j2ee.deployment.config.ModuleDeploymentSupport.getDeploymentDescriptor(ModuleDeploymentSupport.java:111)
	at
org.netbeans.modules.j2ee.deployment.config.ModuleDeploymentSupport.createRoot(ModuleDeploymentSupport.java:115)
	at
org.netbeans.modules.j2ee.deployment.config.ModuleDeploymentSupport.<init>(ModuleDeploymentSupport.java:102)
	at
org.netbeans.modules.j2ee.deployment.config.ConfigSupportImpl.<init>(ConfigSupportImpl.java:93)
	at
org.netbeans.modules.j2ee.deployment.devmodules.spi.J2eeModuleProvider.getConfigSupport(J2eeModuleProvider.java:96)
	at
org.netbeans.modules.j2ee.deployment.devmodules.spi.J2eeModuleProvider.getConfigSupportImpl(J2eeModuleProvider.java:658)
	at
org.netbeans.modules.j2ee.deployment.devmodules.spi.J2eeModuleProvider.access$100(J2eeModuleProvider.java:63)
	at
org.netbeans.modules.j2ee.deployment.devmodules.spi.J2eeModuleProvider$IL.changeDefaultInstance(J2eeModuleProvider.java:644)
	... 40 more

Assigning to Andrei.
Comment 4 Andrei Badea 2006-09-07 17:45:48 UTC
Reproduced. The fix is easy, but the exception is primarily caused by the
project not being garbage-collected after deletion. Needs more evaluation, but
the exception can be fixed for 5.5.
Comment 5 Andrei Badea 2006-09-11 21:02:07 UTC
Filed issue 84650 for the project not being GC'd.
Comment 6 Andrei Badea 2006-09-11 21:03:23 UTC
Fixed the exception.

Checking in src/org/netbeans/modules/j2ee/ejbjarproject/EjbJarProvider.java;
/cvs/j2ee/ejbjarproject/src/org/netbeans/modules/j2ee/ejbjarproject/EjbJarProvider.java,v
 <--  EjbJarProvider.java
new revision: 1.23.36.6.2.14; previous revision: 1.23.36.6.2.13
done