New GlassFish Integration Feature: Profiler Integration Improvements
By vbkraemer on May 21, 2007
Some, like the folks on the profiler team, will argue that this is a bug fix and some, me, would say this is a new feature in the plugin. Regardless of what you call it, this is something that is new in 6.0.
When users tell NetBeans to profile a web application of other Java EE artifact targeted to GlassFish or SJSAS, they see this dialog:
Regardless of what item they picked from the list, the server would start under the JDK indicated by the AS_JAVA setting in the config/asenv.conf (or asenv.bat). This would not be a problem most of the time, since folks would run NetBeans and the App Server under the same JDK. But it could be.
In 6.0, the selected JDK is used to start the app server domain.
Follow this link to a search for all of my entries about new GlassFish integration features for NetBeans 6.0.