[jboss-user] [News & Announcements] - JBossAS 5.0.0.Beta4 released

rrajesh do-not-reply at jboss.com
Mon Feb 11 10:08:18 EST 2008 

JBoss Application Server 5.0.0.Beta4 has been released and is available on sourceforge.

http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=575410

JBoss 5.0.0.Beta4 Release Notes

This is the final Beta release of the JBoss 5.0.x series for the Java EE™ 5 codebase! This release completes a  big round of refactorings related to the transformation of JBossAS into a pure POJO-based server. There should be no API changes from this point on as we move closer to a final release.

For information on the APIs that make up Java EE 5, see Java EE APIs & Docs. A tutorial on Java EE 5 can be found here.

A sample Java EE 5 application that can be run on top of JBoss 5.0.0.Beta4 and demonstrates many interesting technologies is the Seam Booking Application available here. This application makes use of the following technologies running on JBoss 5:

    * EJB3
          o Stateful Session Beans
          o Stateless Session Beans
          o JPA (w/ Hibernate validation)
    * JSF
          o Facelets
          o Ajax4JSF
    * Seam

The JBoss Seam Wiki links to many interesting topics about Seam.
Overview

    * Highlights
    * Compatibility Issues
    * Configuration Issues
    * Other Issues
    * JBoss/Thirdparty Library Updates
    * Detailed Release Notes
    * Additional Docs and Help
    * Licenses
    * About JBoss

Highlights

JBoss 5 is the next generation of the JBoss Application Server build on top of the new JBoss Microcontainer. The JBoss Microcontainer is a lightweight container for managing POJOs, their deployment, configuration and lifecycle. It is a standalone project that replaces the famous JBoss JMX Microkernel of the 3.x and 4.x JBoss series. The Microcontainer integrates nicely with the JBoss framework for Aspect Oriented Programming, JBoss AOP. Support for JMX in JBoss 5 remains strong and MBean services written against the old Microkernel are expected to work.

JBoss5 is designed around the advanced concept of a Virtual Deployment Framework (VDF), that takes the aspect oriented design of many of the earlier JBoss containers and applies it to the deployment layer. Aspectized Deployers operate in a chain over a Virtual File System (VFS), analyze deployments and produce metadata to be used by the JBoss Microcontainer, which in turn instantiates and wires together the various pieces of a deployment, controlling their lifecycle and dependencies.

Many key features of JBoss 5 are provided by integrating other standalone JBoss projects:

    * JBoss EJB3 included with JBoss 5 provides the implementation of the latest revision of the Enterprise Java Beans (EJB) specification. EJB 3.0 is a deep overhaul and simplification of the EJB specification. EJB 3.0's goals are to simplify development, facilitate a test driven approach, and focus more on writing plain old java objects (POJOs) rather than coding against complex EJB APIs.
    * JBoss Messaging is a high performance JMS provider in the JBoss Enterprise Middleware Stack (JEMS), included with JBoss 5 as the default messaging provider. It is also the backbone of the JBoss ESB infrastructure. JBoss Messaging is a complete rewrite of JBossMQ, which is the default JMS provider for the JBoss AS 4.x series.
    * JBossCache 2.0 that comes in two flavors. A traditional tree-structured node-based cache and a PojoCache, an in-memory, transactional, and replicated cache system that allows users to operate on simple POJOs transparently without active user management of either replication or persistency aspects.
    * JBossWS 2 is the web services stack for JBoss 5 providing Java EE compatible web services, JAXWS-2.0.
    * JBoss Transactions is the default transaction manager for JBoss 5. JBoss Transactions is founded on industry proven technology and 18 year history as a leader in distributed transactions, and is one of the most interoperable implementations available.
    * JBoss Web is the Web container in JBoss 5, an implementation based on Apache Tomcat that includes the Apache Portable Runtime (APR) and Tomcat native technologies to achieve scalability and performance characteristics that match and exceed the Apache Http server.

JBoss 5 includes numerous features and bug fixes, many of them carried over upstream from the 4.x codebase. See the Detailed Release Notes section for the full details.
Compatibility Issues

    * JBossAS 5 runs under Java 5 but there is an ongoing task to make it run safely under Java 6, too (JBAS-5031). If using a Sun Java 6 runtime, you may want to set  -Dsun.lang.ClassLoader.allowArraySyntax=true, as described in JBAS-4491.
    * If using proprietary JBoss/EJB3 annotations, those have moved into the org.jboss.ejb3.annotation package, EJBTHREE-1099. Those are now included in a new artifact, jboss-ejb3-ext-api.jar
    * Work on EJB3 Extended Persistence Context support is not completed, EJBTHREE-1026.
    * Interoperating with previous JBoss EJB3 implementations may present problems due to serialVersionUIDs issues, EJBTHREE-1118.
    * EJB 2.1 View requirements
          o Home extending EJBLocalHome? or EJBHome must be defined 
          o Remote or Local interface must either be defined via @Local/@Remote or via return type of "create" methods of the Home 
          o EJB 2.1 Remote/Local interfaces must extend EJBObject/EJBLocalObject
    * @Local/@Remote may be used to define either EJB 3.0 View Business Interface, or EJB 2.1 View Remote/Local interface
    * Use of JBoss Cache 2.x. JBC 2.x has a significantly different API from the 1.x releases used in JBoss AS 4.x and 3.2.x. 

Configuration Issues

This section lists changes that could affect the server configuration.

The directory structure of JBoss 5 resembles that of the 4.x series with some notable differences:

    * bin - start scripts and run.jar
    * client - client jars
    * docs - docs, chemas/dtds, examples
    * lib - core bootstrap jars, somewhat different with the introduction of the microcontainer and breakup of jboss-common.
    * server - the same server configuration dirs.
          o default configuration
                + conf
                      # bootstrap-beans.xml - new mc kernel bootstrap configuration
                      # jax-ws-catalog.xml - oasis catalog driven schema/dtd namespace configuration
                      # jbossjta-properties.xml - new JBossTS properties
                      # jboss-service.xml - legacy static mbeans for compatibility
                      # jndi.properties - the same jndi props
                      # log4j.xml - the same log4j config
                      # login-config.xml - the same jaas login config
                      # props/ - the same default jaas login properties files
                      # standardjaws.xml - obsolete cmp config
                      # standardjbosscmp-jdbc.xml - the same cmp2 config
                      # standardjboss.xml - the same ejb2 config
                      # xmdesc/ - legacy xmbean descriptors
                + deploy/ - the same deploy directory.
                + deployers/ - new vdf deployers
                      # bsh-deployer - beanshell deployer
                      # ejb3.deployer - ejb3 deployers
                      # jboss-aop-jboss5.deployer - aspect deployer
                      # jboss-jca.deployer - JCA deployers
                      # jbossweb.deployer - war deployers
                      # jbossws.deployer - web services deployers
                      # ear-deployer-beans.xml - ear deployers
                      # ejb-deployer-beans.xml - ejb2.x deployers
                      # metadata-beans.xml - metadata handlers
                      # security-deployer-beans.xml - security deployers
                      # profileservice-beans.xml.bak - an example of the repository based profile service
                + lib/ - the same static library jars

Clustering related changes. Check out the Wiki for more info.

    * The clustering configurations have been organized in the deploy dir in a new cluster subfolder (JBAS-4709).
    * A separate cache is now used for Clustered SSO (JBAS-4676).
    * Per webapp configuration of useJK, snapshot mode and snapshot interval (JBAS-3460). Default for useJK is whether jvmRoute is set (JBAS-4961).
    * Setting of default clustering metadata removed from the Web Deployer (JBAS-4967). 

EJB3 configuration  is now controlled by deployers/ejb3.deployer/META-INF/ejb3-deployers-beans.xml. For more details check out this wiki page.

For security related configuration changes, please consult this wiki page.
Other Issues

    * Hot deployment is enabled, however undeployment on Windows, by removing files from the ./deploy directory  is problematic due to jar files being locked, JBAS-4310.
    * Excessive nestedjarNNN.tmp files in the tmp directory. The VFS unwraps nested jars by extracting the nested jar into a tmp file in the java tmp directory. This can result in a large number of files that fill up the tmp directory. You can disable this behavior by setting -Djboss.vfs.forceNoCopy=true on command line used to start jboss. This will be enabled by default in a future release, JBAS-4389.
    * The Farm service is removed. Distributed deployments will eventually be handled by the AS 5 Profile Service, with the Profile Service (or JBoss ON) coordinating deployments across the cluster from a centralized repository. The Farm Service's function of replicating deployment archives between file systems will not be maintained.
    * The JSR77 view of the server is not implemented yet.
    * There is a noticable delay (10-15secs) in the start-up time of the application server. This is due to annotation processing from the AOP subsystem and is scheduled to be corrected in the CR release, JBAS-5224.

Library Updates
For a full list of the JBoss and thirdparty libraries used with JBoss AS 5.0.0.Beta4 see  build-thirdparty.xml.

Changes:
Detailed Release Notes
Includes versions: JBossAS-5.0.0.Beta4
Feature Request

    * [JBAS-1451] - Need additional trace level logging about security domain cache validation
    * [JBAS-2283] - Custom header based authentication
    * [JBAS-2499] - Add configurable policy for determining master node for HASingleton
    * [JBAS-2936] - Upgrade JBossSerialization to 1.0.0.CR4
    * [JBAS-3323] - Role Mapping Login Module that maps application role to declarative role
    * [JBAS-3583] - HAPartition should use its Marshaller for marshalling RPC responses
    * [JBAS-3587] - Add a system property to configure TCPPING.initial_hosts
    * [JBAS-3588] - Add system property to configure multiplexer stack
    * [JBAS-3815] - Deployment Level Principal-Role Mapping passed to authorization layer
    * [JBAS-3851] - Slow DataSource Failover - JCA Stale Connection Detection
    * [JBAS-3870] - Clone the JBossMX javax.management.timer.Timer implementation, to a jboss package
    * [JBAS-4455] - LoadBalancePolicy that tries to pin all requests associated with a tx to one server
    * [JBAS-4543] - Make HAServiceMBeanSupport "bean name aware"
    * [JBAS-5139] - Support injection-target properties within service-ref declarations
    * [JBAS-5180] - Make ClusterPartition mbean queryable
    * [JBAS-5183] - Provide info as to whether topology changes are due to a merge
    * [JBAS-5196] - Add a jboss.messaging.ServerPeerID system property to ServerPeer configuration in messaging-service.xml
    * [JBAS-5215] - Temporary fix: Set TCL and BeanMetaData classloader to the deployment classloader in TempBeanMetaDataDeployer

Bug

    * [JBAS-1571] - Logging of cluster rpc method exceptions at warn level is incorrect
    * [JBAS-1926] - two timers executing at the same time in some conditions
    * [JBAS-2188] - "jboss:service=invoker,type=http,target=HAJNDI" misconfigured in file httpha-invoker.sar/META-INF/jboss-service.xml
    * [JBAS-2403] - JBossCacheManager session expiration algorithm ignores replication events
    * [JBAS-2428] - Lock Contention on org.jboss.ejb.BeanLockManager
    * [JBAS-2429] - Clustered SSO improperly invalidated upon web application shutdown
    * [JBAS-2564] - hashCode() of org.jboss.util.id.GUID and UID appears to return the same value for all GUIDs created
    * [JBAS-2585] - Lock contention on BasicMBeanRegistry::get
    * [JBAS-2586] - Synchronization into org.jboss.ejb.EnterpriseContext$EJBContextImpl
    * [JBAS-3198] - Problems with separated ClassLoaders for EARs and pooled invoker (PooledInvokerHA).
    * [JBAS-3279] - Authenticated user can bypass declarative role checks for servlets
    * [JBAS-3438] - LdapExtLoginModule does not handle roles containing '/' correctly
    * [JBAS-3794] - Remove all calls to InetAddress.getHostName() (causes reverse DNS lookup)
    * [JBAS-3883] - JBoss ignores "Class-Path" attribute in WAR's MANIFEST.MF
    * [JBAS-4292] - Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test failures
    * [JBAS-4313] - Cluster loses his master
    * [JBAS-4322] - Wrong context path in Embedded JBoss JAR deployment
    * [JBAS-4333] - JBoss DD shemas should use a jboss specific namespace
    * [JBAS-4491] - Server startup failure with JDK 1.6
    * [JBAS-4763] - Depends element in jboss-web.xml ignored
    * [JBAS-4919] - HASingletonElectionPolicySimple does not handle heterogeneous topologies
    * [JBAS-4943] - jboss-ds_1_5.dtd is wrong
    * [JBAS-5050] - web-console doesn't start
    * [JBAS-5066] - InstanceInterceptors need to set SecurityContext on EnterpriseContext from Threadlocal
    * [JBAS-5068] - Possible NullPointerException in DistributedReplicantManager#_add()
    * [JBAS-5074] - MarshalledInvocation constructor should copy over all invocation attributes
    * [JBAS-5091] - BuddyCommunicationTimeout is too low
    * [JBAS-5097] - MessageDestinationReferenceMetaData produced by merge of annotation and xml loses information
    * [JBAS-5105] - PostgreSQL Entity Command for jdbc2pm is Not Working Properly
    * [JBAS-5107] - jboss-aop-jdk50-client.jar missing classes
    * [JBAS-5136] - AnnotationMetaDataDeployer queries isMetadataComplete on JBossMetaData before a merge has taken place
    * [JBAS-5140] - NPE in MergedJBossMetaDataDeployer merging security roles
    * [JBAS-5142] - cmp2.x jdbc2 pm: missing a join in a collection path translating "member of"
    * [JBAS-5150] - EJB Corba servants need to set Security Context on invocation for remote calls
    * [JBAS-5155] - DistributedReplicantManager - Add lookup method to that given a replicant name, returns a List of ClusterNode
    * [JBAS-5164] - Generic ProxyFactoryHA leaves proxy in JNDI after undeploy
    * [JBAS-5171] - TxConnectionManager is track-connection-by-tx false by default
    * [JBAS-5175] - The profile service bootstrap should undeploy in reverse deployment phase order
    * [JBAS-5186] - Incorrect service name in org.jboss.tutorial.webservice.client.Client
    * [JBAS-5188] - RoleBasedAuthorizationInterceptorv2 needs to set the contextid on the PolicyContext
    * [JBAS-5194] - DataSource connection properties should use a CompositeMetaType/CompositeValue
    * [JBAS-5205] - AnnotationMetaDataDeployer attempts to load all dependencies
    * [JBAS-5212] - NPE at org.jboss.aop.pointcut.FieldMatcher.visit(FieldMatcher.java:181) at shutdown
    * [JBAS-5214] - ServiceControllerLifecycleCallback.uninstall() should unregister mbean
    * [JBAS-5217] - Security Deployer issue with conflicting war names in multiple EARs

Task

    * [JBAS-1617] - Merge fixes for JacORB bugs #562 and #568 into the JacORB lib shipped w/ JBoss
    * [JBAS-2040] - Spring Deployer
    * [JBAS-2505] - Hibernate integration in JBoss5
    * [JBAS-2522] - Integration of JGroups 2.2.9 final with JBossAS 5
    * [JBAS-3170] - ProfileService Bootstrapping of the MC
    * [JBAS-3218] - Handle expiration of replicated sessions found in the buddy replication subtree
    * [JBAS-3410] - VDF Deployer migration tasks
    * [JBAS-4148] - Replace Gjt code used in the ejb 2.x validation phase
    * [JBAS-4180] - Reduce coupling between JMX and HASingleton
    * [JBAS-4215] - Need to externalize the web container class loader to use outside of the web container
    * [JBAS-4276] - Replace injection of PartitionName or ClusterPartitionMBean with HAPartition
    * [JBAS-4378] - Update the management CRUD usecases
    * [JBAS-4647] - Track jboss and thirdparty dependencies upgrades for JBoss 5.0.0.Beta4
    * [JBAS-4706] - Deployer to synchronize meta data after the unguaranteed parsing deployers
    * [JBAS-4762] - Make distributable webapps depend on the clustering cache
    * [JBAS-4997] - Package StatefulPassivationActivationUnitTestCase with its own HAPartition
    * [JBAS-5016] - Make release notes for Beta4
    * [JBAS-5059] - Update Service Binding configuration for JBossMessaging
    * [JBAS-5060] - Upgrade jfreechart to v1.0.2
    * [JBAS-5062] - AudtManager should be on demand
    * [JBAS-5077] - JBoss Messaging ServerPeer refactorings for better JBossAS integration
    * [JBAS-5086] - Remove deprecated JGroups properties from multiplexer-stacks.xml
    * [JBAS-5098] - Performance Issues
    * [JBAS-5101] - Re-enable JGroups message bundling
    * [JBAS-5104] - Upgrade JBossMessaging to 1.4.0.SP3
    * [JBAS-5153] - Pull web class loader creation into WarClassLoaderDeployer
    * [JBAS-5181] - Inject MBeanServer into JChannelFactory
    * [JBAS-5191] - Manage JBoss Web runtime lifecycle via a JMX service in deploy
    * [JBAS-5193] - Separate HAPartition deployment from other cluster services
    * [JBAS-5207] - Upgrade Hibernate EntityManager to 3.3.2.Beta3





View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128397#4128397

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128397

More information about the jboss-user mailing list