GlassFish v3. Building an ex tensible modular Java EE application server. Jerome Dochez and Ludovic Champenois Sun Microsystems, Inc.

Transcription

1 GlassFish v3 Building an ex tensible modular Java EE application server Jerome Dochez and Ludovic Champenois Sun Microsystems, Inc.

2 Agenda Java EE 6 and GlassFish V3 Modularity, Runtime Service Based Architecture Containers inside out OSGi integration

3 GlassFish V3 Java EE 6 (and previous releases) Profiles Web- developer productivity Modularity Grow from minimal (3mb) to full Java EE support and more... Based on OSGi Embedded Start using Java EE 6 platform features in your Java SE application (JPA, local ejb...) API driven

4 GlassFish V3 product differentiation Open for all JVM based technologies JRuby/ Grails Native deployment (no war repackaging) Extensible Ex tensive APIs to replace or ex tend features OSGi also provides extensions capabilities Service based architecture services are defined by contracts and can be easily substituted lazy loading based on usage patterns

5 Agenda Java EE 6 and GlassFish V3 Modularity, Runtime Service Based Architecture Containers inside out OSGi integration

6 Why modularity can be important to you Just an Implementation detail? Java EE Profiles requires it Uses cases can leverage modularity Disgruntled joe programmer Fat web app. Service based architecture Integration of disparate technologies (OSGi) Your own extensions or container!

7 Disgruntled joe programmer Only use part of the Java EE stack Cannot unit test his applications as part of the build Tired of slow startup and slow deployments Would like to experiment new technologies without updating the entire stack

8 Fat Web Application > 30Mb web applications Co- bundle libraries Co- bundle services Three tier application in one huge application Iterative development is hell Updating one service requires re- deployment of the entire application

9 Service Based Architecture EJB, Spring, WebBeans all require co- bundling unless CORBA is used. One service update should be transparent to the system Adding/ removing services implementation should be possible. Java EE 6 not entirely providing a solution either.

10 Your own extensions/ container Plugins to administer your application configuration AdminGUI CLI Command Modifying an existing container (e.g. Spring) requires in place modification as you cannot plugin the deployment backend Adding new types of application, container can be a simple solution to in- house components with specific lifecycle/ invocations requirements

11 Modularity Based on OSGi GlassFish v3 is delivered as 170 bundles Undoubtedly too many... Successfully maintained quick startup Modules nomenclature Services they provide Lifecycle Strong build tool is necessary, we used maven Used to deliver Java EE profiles

12 GlassFish Developer Features Integration with NetBeans, Eclipse, IntelliJ Fast startup, restart in debug mode Exploded directory deployment Fast Deploy on save Preserve Session across redeployment Application runner: Java - jar glassfish.jar mywebapplication Maven/ ANT Integration Award winning UI console Active community and Forums

13 Demo 1

14 Runtime Kernel startup/ shutdown sequences basic services (deployment) configuration reading Services Cross containers functionalities Java EE 6 : Security, Naming Manager... Products : Admin Console Containers handle user's applications independent of each others

15 Container Isolation (Java EE 6 Profiles) WEB EJB Persistence WebServices... Glue Glue Glue Glue Kernel, OSGi, basic services Optional Services

16 Application Container Deployment Ability to add/ remove/ start/ stop applications Configuration Ability to have configuration stored in central configuration Automatic clustering support Commands CLI, REST invocations Monitoring (MBeans, Gmbal)

17 Agenda Java EE 6 and GlassFish V3 Modularity, Runtime Service Based Architecture Containers inside out OSGi integration

18 Service Based Architecture Modules are just packaging artifact Capabilities and relationships are formed using services OSGi services HK2 services Abstraction to OSGi services Per thread/ Per request scopes Integrated lightweight dependency injection

19 HK2 Service Interfaces are declared Implementations are declared Build system will generate Metadata public interface Startup public class ConfigService implements Startup {... }

20 Service Lookup Dependency Public class RandomService implements SomeCtr Startup somestartupservice } Autom atic cascading Nam e resolution e= foo ) Can be API driven (no DI)

21 Agenda Java EE 6 and GlassFish V3 Modularity, Runtime Service Based Architecture Containers inside out OSGi integration

22 Application Container Runtime C O N T A I N E R G l u e C o d e K e Kernel r n e l Deployment Configuration Grizzly Monitoring AdminGUI

23 Configuration Configuration is defined by annotated POJIs Lands in our central config (domain.xml) Automatic clustering support Automatic MBeans generation Automatic REST interface Automatic transaction access to mutating data Well integrated product, yet made of disparate bits and pieces. All configuration interfaces are implemented by a single class we own, very lightweight.

24 REST Use JAX- RS to provide REST interfaces to Configuration data Commands invocation (deploy, undeploy, etc..) Monitoring Binding use annotations configuration command implementations to generate WADL. / localhost:4848/ restresources/ domain You can even use REST clients as an AdminGUI substitute

25 CLI Administrative commands can be added with each container : Manipulates the container change- random- ctr ) public class ChangeRandomCtr implements AdminCommand String String s2; } Available as : asadmin change- random- ctr s1 foo s2 bar

26 Agenda Java EE 6 and GlassFish V3 Modularity, Runtime Service Based Architecture Containers inside out OSGi integration

27 27 OSGi integration No OSGi APIs are used in GlassFish v3 Hk2 provides isolation layer Mockup implementation of hk2 makes V3 capable of running without OSGi Embedded mode Static mode (single class loader) All GlassFish modules are OSGi bundles Completely portable to any OSGi R4 compliant runtime Felix is the default

28 OSGi services implemented in v3 HTTP Service Simple dynamic servlet web server OSGi Alliance RFC 98 Transactions in OSGi OSGi Alliance RFC 66 OSGi- based web container

29 OSGi integration Module management Add, remove, update installed modules OSGi as a container! Treat OSGi just like any container, bundles are deployed to it. Can leverage OSGi to extend Glassfish Converged Applications Started investigating Java EE 6 + OSGi converged applications : Dependencies in OSGi Lifecycle still governed by Java EE.

30 OSGi Integration (2) OSGi services Available to any Java EE osginame ) SomeOSGiService injectedservice; JNDI lookup Portable, no OSGi dependencies in your Java EE application code No bundle management access All installed bundles exported APIs visible to Java EE Applications

31 Jerome Dochez Sun Microsystems, Inc.