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.
Most profilers give the developer the possibility to compile the profiled application against some small-ish API, and be able to turn on/off instrumentation and obtaining results from within the profiled application using code. This is a commonly used feature by the NetBeans profiling team, indicating that it might be one of those things that in real life can really help to get focused/specific results.
Will not be public in 1.0
Not for 1.0
We develop WWW application written (among other things) in Java and running under Tomcat or EAS Server. We have automated tests of the application written in Java too. Now we want to be sure at the end of each test that there isn't any non- released instance of the class XYZ in the application's memory. So, we’d like to call (at the end of each test) Java code which make a memory snapshot of the application and check existence of any non-released XYZ instance in it. We have a similar plan with instances of the class OPQ, we just want to be sure, that there is exactly one OPQ's instance at the end of each test. So, Java API would be very useful for us.
Note that Profiling Points feature is available in devbuilds of Profiler 6.0, which are at the time replacement for profiling API.
Milestone cleanup: future->next