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.
Add ability to profile J2EE (EJB/EAR) projects in the NB 4.1 IDE, preferably out-of-the box, similarly to how debugger is able to debug them.
Planned for M6
I suggest that startup of the bundled AS in profiling mode is tracked in a separate issue (54572), since it is a separate problem and may take longer to solve due to dependencies on the rest of NB. This issue (53645) should cover possible special features/enhancements that we almost certainly need to introduce to make profiling J2EE apps manageable for the user. They can hopefully be used independently of whether we start the AS "out-of-the-box" or not. So far the following features have been suggested: 1. Pre-selection of "key" methods, such as J2EE app business methods, as instrumentation roots for selective profiling. 2. Aggregation of results into single CCT for multiple threads. Feel free to extend this list.
Self assign
Postponing to M7, since most of the stuff this needs is not implemented yet (and may not be in 1.0). Logging dependency on Issue 51274
Startup of Web/App server in profiling mode is solved in http://www.netbeans.org/issues/show_bug.cgi?id=54572. Aggregation of results into single CCT is solved in http://www.netbeans.org/issues/show_bug.cgi?id=51274. Because of this I'm renaming this issue to better reflect remaining feature - automatic/assisted selection of root methods for web/j2ee project.
Postponed to M8
Implemented for WebProjects.
Only WebProjects will be supported in 1.0, so I'm closing this issue as fixed. Support for other project types will be tracked in separate issue.
*** Issue 61816 has been marked as a duplicate of this issue. ***
Verification of old issues.
Closing old issues.