GlassFish V3 Developer Experience Improvements

%%sortable

Feature-ID Desired Improvement Priority Comments Issue Link Eng Response
DEVEX-1 Enhance NetBeans support P1 Enhance plugin (Ex: support deployment of scripting languages to "native" GlassFish V3 modules, Java EE 6 apps)   Yes
DEVEX-2 Enhance Eclipse support P1 Enhance plugin (Ex: support deployment of scripting languages to "native" GlassFish V3 modules, Java EE 6 apps)   Yes
DEVEX-3 Add product samples P1 Add product samples for Java EE 6, JRuby and PHP   Yes
DEVEX-4 Tutorial and blueprints update P1 Update Java EE tutorial and blueprints to Java EE 6.   Partial, Tutorial only.
DEVEX-5 Allow the creation of Unit tests for EJB's by making an embedded Glassfish, much like embedded JBoss P3 Community request . The assumption is that this is for an EJB-only embedded container. The GlassFish V3 lazy-load requirement and embedded requirement (DEVEX-11) should be enough to address this community request.   Yes
DEVEX-6 Improve error messages and error handling. P1 Shorter time to problem resolution (community request ) (2nd request )   Yes
DEVEX-7 Removed - See OSGi requirement ) (Community request ).
DEVEX-8 Remember location when uploading EAR from admin console P2 (Community Request )   Maybe. Investigate further, move to admin GUI section
DEVEX-9 Maven integration P2 Multiple community requests (here ) (here )   Yes
DEVEX-10 AOP Framework support P3 From Community : Other app servers integrate AOP frameworks which can be very efficient in solving some application level design and monitoring issues. GF should include such a framework   No
DEVEX-11 GlassFish should be embeddable within an existing JVM P1 This is useful to improve the development experience (example: Phobos as well as being useful for OEMs in general.   Yes, with some limitations.
DEVEX-12 Extend web services management testing capability to include JBI-based services P2 Requested by Open ESB community.   No.
DEVEX-13 Dynamically reload application class files without losing application state P1 (Community Request ). Developer productivity feature. Developers will get same rapid round trip development experience whether using JRuby, PHP or Java.   Yes

%%