Improvements:

• Services
  • New 'jaxws' service for JAX-WS support
• Components upgrade
  • OW2 EasyBeans (1.1.0.M1)
  • OW2 Utils (1.0.9)
  • OW2 CMI (2.0.10)
  • OW2 Carol (3.0)
  • OW2 JORAM (5.1.0a)
  • Apache Tomcat  (6.0.18)
  • Apache CXF (2.0.7)
  • Apache Felix (1.0.3)
  • Hibernate (core:3.3.1.GA, entitymanager:3.4.0.GA)
• lib/ext/✶.jar auto bundlization
  • Each library found in this folder will be transformed into an OSGi bundle (Export everything, DynamicImport-Package *).
  • Note that it is better to customize the import/export of your library and not use this default mechanism.
  • Ease JDBC drivers usage for example
• Client side injection (@EJB or @Resource can be put in the client class launched by the Client Container)
• EJB3/OSGi Advanced usage
  • EJB3s packaged as bundles now have there business interfaces registered as OSGi services
  • EJB3s services supports the ManagedService interface (ConfigurationAdmin) for service's properties modifications
• JonasAdmin console allows service life-cycle management (stop/start button in the Services page).

New features:

• Deployment Plans

• XML files that describe a succession of resources (local or remote) that must be deployed in the given order.
• Support of three repository types: URL, Maven2 and OBR (OSGi Bundle Repository)
  • URL can simply be a directory (local or remote) where deployable artifacts can be found
  • Maven2 describes a Maven2 structured repository
  • OBR describes an OBR repository (example)
• Resources will downloaded if needed
• Examples can be found under $JONAS_BASE/conf/deploy
  • Used during JOnAS startup, given the activated services (jonas.services)

• Service on demand

• New mechanism allowing applications (aka Java EE archives) to describe wich plan they need in order to run.
• JOnAS services (like web, ejb, ...) can be required for an application (each have a plan)
  • The associated deployment plan (see above) will be used and described resources will be installed on JOnAS
  • Required service is then started
• Required plans are declared in the META-INF/MANIFEST.MF of the Java EE archives
  • Attribute's name: Require-JOnAS-Services
• For example jonasAdmin.war requires the 'admin-tools' plan to be installed and started before deployment

• JAX-WS 2.0

• Initial support of EJB3 Session Beans exposed as WebServices
  • @WebService support
• Initial support of @WebServiceRef based injection
  • Works for web applications

• Flex Administration Console

• jonasAdmin re-engineering using Rich Interface Technologies
  • Domain Management
  • Domain Monitoring
• Based on Adobe Flex
• Highly interactive and dynamic
• Still EXPERIMENTAL, but feedback is welcomed
  • Old pages are still available

• In order to test the new Flex based domain management:

• Start a master server (jonas.master property in jonas.properties must be set to true)
• Open http://localhost:9000/jonasAdmin using a Flash enabled browser.
• Select the Domain/Flex node in the management tree.

New Domain visualization tool using graphs	New Domain status overview using pie charts

Documentation

Update of the documentation.

Bug fixes.

Best Regards,

JOnAS Team