Copyright © 2007 Red Hat, Inc.
Abstract
These are the Release Notes for the JBoss Enterprise Application Platform 4.2.0.CP01 Release, containing late breaking and important information
Looking for a powerful tool for developing rich, high performance, Web 2.0 applications on a pure Java Platform?
JBoss Enterprise Application Platform 4.2 is the next evolutionary step in open source enterprise software.
It provides complete compatibility with existing J2EE 1.4 enterprise Java applications.
At the same time, almost all the key features and components defined in the Java EE 5.0 specification are supported. So your new enterprise Java applications can take immediate advantage of the Java EE 5.0's significantly simpler POJO-based programming model.
Further, by integrating best-of-breed open source frameworks -- such as JBoss Seam, Hibernate, Tomcat, and JBoss Cache -- the JBoss Enterprise Application Platform takes advantage of innovations in the open source community.
As well, JBoss Enterprise Application Platform 4.2 is fully tested and supported by Red Hat, and is certified to work on many leading enterprise hardware and software products.
All of which means you can develop your new application taking advantage of Java EE 5.0 technologies immediately and with the confidence of knowing it will remain forward-compatible with future versions of the JBoss Platform.
http://www.redhat.com/support/process/
http://www.redhat.com/support/policy/soc/production
http://www.redhat.com/support/policy/sla/production/
http://www.redhat.com/support/policy/soc/developer/
http://www.redhat.com/support/policy/sla/developer/
http://www.redhat.com/security/updates/jboss_notes/
In the zip distribution, documentation for the Platform and its individual components is distributed in a separate zip file, jboss-eap-docs-<version>.zip.
On a Linux system, the documentation is found in two rpms that will need to be installed manually. These rpms are jboss-seam-docs-<version>.noarch.rpm, and rh-eap-docs-<version>.noarch.rpm. For help with installing rpm packages on Red Hat Enterprise Linux, please refer to the Red Hat Knowledge base article located at http://kbase.redhat.com/faq/FAQ_35_198.shtm
Updated versions of the documentation with errata and additional information, as well as example application code, may be accessed via the web from http://www.redhat.com/docs/manuals/jboss
See the index.html file in the documentation directory for a list of included documentation.
Please refer to http://www.redhat.com/docs/manuals/jboss/ for the most recent version of the release notes.
If you are using the rpm, or the zip distribution, please note that by default, authentication is enabled and no user accounts are set up. This is done to prevent unauthorized access to various services of JBoss AS. Please refer to the Installation Guide, or see http://kbase.redhat.com/faq/FAQ_107_9963.shtm for information on how to make the services accessible again.
It is recommended to run the example Seam applications that are included with the documentation using the production configuration. Using another configuration may result in memory issues. Note that the default configuration for the server to start with, if no other configuration is specified, is the production configuration.
Seam is upgraded to version 1.2.1.GA in this release.
Please note that the embedded Hypersonic Database is included as a technology preview and is not supported for use in production environments. Technical support is not available for this component, and while we are happy to accept bugs filed against this component, we do not make any commitment to fix them within a specific timeframe.
JSR-181 related functionality is not supported in this version of the JBoss Enterprise Application Platform. This functionality will be supported in version 4.3.
Following is a list of issues fixed in this release:
JBPAPP-317: Fix multiple potential vulnerabilities in embedded Tomcats
JBPAPP-239: org.jboss.web.tomcat set to DEBUG in the production config
JBPAPP-316: JBossWS - init-param for handler defined in jaxrpc-config not processed
JBPAPP-280: JBossWS - WSDL To Java - Array Unwrapping uses incorect case to reference array type.
JBPAPP-274: JBossWS - Post-handler-chain not invoked for "Standard Client" configuration with DII client
JBPAPP-257: JBossWS - Incorrect handling of charsets when the default charset is not UTF-8
JBPAPP-278: JBossWS - WSDL To Java - Add support for bound headers.
JBPAPP-307: JBossXB - JAXB error when using different derived types in the same container/array type
JBPAPP-293: JBossWS - WSDL-JAVA Derivation of a complex type from a Simple type: bas64Binary is not mapped to byte
JBPAPP-282: JBossWS - WSDL To Java - Initial Character of Service and SEI names should be upper case.
JBPAPP-300: WSDL To Java - Anonymous Types Referenced As Bound Headers Not Handled Correctly
JBPAPP-289: JBossWS - WSDL To Java - Incorrect handling of Simple types derived by restriction for holders.
JBPAPP-276: JBossWS - Post-handler-chain not invoked for "Standard Client" configuration
JBPAPP-299: JBossWS - WSDL To Java - Create Custom Holders for Custom types that define INOUT parameters and OUT parameters
JBPAPP-291: JBossWS - NPE in WSDL to Java when webservices.xml requested but no global package mapping
JBPAPP-288: JBossWS - WSDL To Java - Incorrect handling of Simple types derived by restriction for holders.
JBPAPP-302: Fix Tomcat security vulnerabilities, CVE-2007-3382 and CVE-2007-3385
JBPAPP-313: JBPAPP-258 - ANN-551 Guarantee the same parameter ordering when overriding SQL across VMs and compilations
JBPAPP-296: JBWEB-89 StringIndexOutOfBoundsException in JvmRouteValve.handleJvmRoute()
JBPAPP-252: org.jboss.remoting.transport.Connector should unregister server invoker from MBeanServer
JBPAPP-245: JBAS-4540: Port 8083, HTTP request revealing installation directory
JBPAPP-284: JBossWS - WSDL To Java - If fault name contains 'Fault' the generated Exception does not match the throws clause on the SEI
JBPAPP-268: JBossWS - MessageFactory does not preserve comments and text nodes.
JBPAPP-314: Upgrade Remoting to 2.2.2.GA to support JBM and fix several issues
JBPAPP-264: HTTPClientInvoker Doesn't Handle Long UserID/Pass Combos For HTTP BASIC Auth
JBPAPP-229: EJBTHREE-994 - Multiple remote bindings is not working
JBPAPP-263: EJBTHREE-942 support RemoteBindings annotations from ejb3-interceptors-aop.xml
JBPAPP-261: EJBTHREE-1022 - system properties replacement for sub-values
JBPAPP-260: EJBTHREE-975 - HA-JNDI InitialContext for @Resource annotation
JBPAPP-259: EJBTHREE-997 - implement and create test for security-role-ref
JBPAPP-202: production configuration for Windows requires updating
JBPAPP-286: JBossWS - WSDL To Java - document/literal, IN OUT parameter incorectly used as return type.
JBPAPP-242: Move patches added during rpmbuild, into svn
JBPAPP-254: Clustered Console's web.xml uses wrong system property for HA cluster's mcast port
JBPAPP-312: JBPAPP-253: -Run.sh fails if -c command line argument is 10 or more arguments down
JBPAPP-176: org.jboss.test.util.test.TwiddleUnitTestCase cannot connect to host
JBPAPP-318: JBSEAM-997: Hot deploy of Seam components in a WAR
Following is a list of known issues at the time of release. Further details on these issues can be found in JIRA.
JPBAPP-310: JBossCache - Heuristic outcome (STATUS_UNKNOWN) of transaction not handled properly
JBPAPP-306: JBCACHE - Memory leak in PojoCache undo list
JBPAPP-305: JBCACHE- Setting Option ineffective if CacheLoader or BuddyReplication is used