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 53711 - Exception from profiler when creating Populated J2EE App
Summary: Exception from profiler when creating Populated J2EE App
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: All Windows XP
: P2 blocker (vote)
Assignee: iformanek
URL:
Keywords:
: 53712 (view as bug list)
Depends on: 53884
Blocks:
  Show dependency tree
 
Reported: 2005-01-19 19:26 UTC by _ tboudreau
Modified: 2007-02-12 22:08 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Patch for M4 to fix this issue (15.23 KB, application/octet-stream)
2005-01-25 09:43 UTC, iformanek 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description _ tboudreau 2005-01-19 19:26:34 UTC 
With the profiler installed, M4, creating a new Populated J2EE 
App, an NPE is thrown after the wizard completes, from the 
profiler (will attach stack trace later - it's on my other machine).  
Anyway, it is reproducible.

I suspect it is making some sort of wrong assumptions about it 
being a freeform project (or possibly you're being passed null, 
but AFAIK it works fine when the profiler is not installed.

Anyway, if you want to demo both the J2EE stuff in NetBeans and 
the Profiler, the result is quite embarrassing.
Comment 1 mishadmitriev 2005-01-20 07:37:15 UTC 
*** Issue 53712 has been marked as a duplicate of this issue. ***
Comment 2 mishadmitriev 2005-01-20 07:38:46 UTC 
Would be nice if we could produce a "hotfix" for Tim, in the same way 
we routinely do that for other users. I can imagine this demoeing 
nightmare quite well.
Comment 3 iformanek 2005-01-24 12:57:07 UTC 
Fixed for M5.
The EarProject returns null from project.getLookup 
(AuxiliaryConfiguration.class). 

The fix is in checking if the returned value is null. Will file an 
issue agains J2EE support, since the profiler needs this to recognize 
the J2EE project type - as it does for Freeform and J2SE projects.
Comment 4 _ tboudreau 2005-01-24 16:12:35 UTC 
Thanks, Ian.  If somebody could get a fixed build of it into my hands quickly, I'd appreciate it 
- I've got more demoing to do, and it will make that go more smoothly.
Comment 5 iformanek 2005-01-25 09:43:39 UTC 
Created attachment 19929 [details]
Patch for M4 to fix this issue
Comment 6 iformanek 2005-01-25 09:44:54 UTC 
To use the patch, replace the two profiler modules in modules/eager 
with their counterparts from the attached ZIP file.
Comment 7 ehucka 2006-10-09 12:10:51 UTC 
Verification of old issues.
Comment 8 Alexander Kouznetsov 2007-02-12 22:08:03 UTC 
Closing old issues.