Copyright © 2008 Red Hat, Inc
Copyright © 2008 Red Hat, Inc. This material may only be distributed subject to the terms and conditions set forth in the Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License (which is presently available at http://creativecommons.org/licenses/by-nc-sa/3.0/).
Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of Red Hat, Inc. in the United States and other countries.
All other trademarks referenced herein are the property of their respective owners.
The GPG fingerprint of the security@redhat.com key is:
CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E
1801 Varsity Drive
Raleigh, NC 27606-2072USAPhone: +1 919 754 3700
Phone: 888 733 4281
Fax: +1 919 754 3701
PO Box 13588Research Triangle Park, NC 27709USA
These release notes contain important information related to JBoss Enterprise Application Platform 4.3 CP02 FP01 that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing JBoss Enterprise Application Platform 4.3 CP02 FP01 Feature Pack.
JBoss Enterprise Application Platform is the next evolutionary step in open source enterprise software. It is a powerful tool for developing rich, high performance, Web 2.0 applications on a pure Java Platform.
This feature pack provides a fully supported way to upgrade Seam currently included in EAP (Enterprise App Platform) 4.3 to the latest stable, production release (Seam 2.0.2.FP). It also includes a Technology Preview of Hibernate Search 3.0.
A Feature Pack is a mechanism to add new features to a product outside of the routine major release schedule. All fully supported features included in this feature pack will be included in the next major release of the product (i.e. EAP 5.0). All those features marked Technology Preview in this Feature Pack will also be candidates for inclusion in the next major platform release; though some may still be designated as a Technology Preview.
Seam 2.0.2.FP
Integration with SOA-P 4.3.0.GA
Integration with jBPM 3.2.2
Integration with Drools 4.0.7
Integration with Hibernate Core 3.2, Annotations 3.3, Entity Manager 3.3
Integration with RichFaces 3.1
Hibernate Search 3.0
Integration with GWT 1.4
Integration with Groovy 1.5
Integration with Spring Framework 2.0
ICEfaces support for Groovy and the Spring Framework 2.0
GWT, Groovy and Spring Framework are not included in this Feature Pack and are not currently supported by Red Hat.
This section contains information related to installing JBoss Enterprise Application Platform Feature Pack version 4.3.0_CP02_FP01, including hardware and platform requirements and prerequisites.
To install this Feature Pack, unpack the contents of the archive into the root of your JBoss Enterprise Application Platform installation, which must be version 4.3.0_CP02.
The contents of the Feature Pack should not be placed within a seperate folder in the EAP directory, but instead it should be intergrated with the current installation.
You must have adequate disk space to install the EAP Feature Pack while also allowing enough space for your applications. You must have a working installation of JDK 1.5 or JDK 1.6 (JDK6) and JBoss Enterprise Application Platform 4.3.0_CP02. For the latest information on supported Operating System / JVM combinations, supported Database platforms and current information on the revision level of included components, please refer to http://www.jboss.com/products/platforms/application/testedconfigurations.
Software channels provide a well-defined method to determine which packages should be available to a system for installation or upgrade, based upon its operating systems, packages, and functionality. After logging in to your account on the RHN website at http://rhn.redhat.com you can click on a channel name to view its Channel Details page.
You can use the following steps to subscribe a system to the Application Platform channel. This channel will only be available for a valid subscription. Use the Channels tab to view the software channels available for your account.
For a system that is already registered to Red Hat Network (RHN), log in to your account.
Select the Systems tab along the top menu. This will bring up the System Overview.
If the System Overview menu shows System Groups, select View Systems, to see the Systems list.
Select the desired system by clicking the system name link under the System column.
Select the Alter Channel Subscriptions link under the Subscribed Channels section (on the right side of the page).
To modify the child channels associated with this system, use the checkboxes next to the channels and click the Change Subscriptions button. You will receive a success message or be notified of any errors.
Subscribe to the child channels:
jbappplatform-4.3.0-[i386|x86_64]-as-4-rpm
jbappplatform-4.3.0-fp-[i386|x86_64]-as-4-rpm
Run the following command:
up2date jbossas jboss-seam2 rh-eap-docs jboss-profilerSubscribe to the child channels:
jbappplatform-4.3.0-[i386|x86_64]-server-5-rpm
jbappplatform-4.3.0-fp-[i386|x86_64]-server-5-rpm
Run the following command:
yum install jboss-seam2 hibernate3-validator rh-eap-docs jboss-profilerInstallation of the documentation (rh-eap-docs) and the log-based event profiler (jboss-profiler) are optional but recommended as these will assist you in understanding and troubleshooting the JBoss Enterprise Application Platform.
For instructions on how to migrate your system from Seam 1.2 to Seam 2, refer to chapter 4 of the Seam Reference Guide included with this Feature Pack release. This chapter will guide you through the process.
Refer to the index.html file in the documentation directory for a list of included documentation.
Updated versions of the documentation with errata and additional information, as well as the most recent version of the release notes may be accessed via the web from http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/.
Following is a list of issues and features applied in this release:
Seam 2.0.2.FP which is included within this Feature Pack now deploys to the EAP production server configuration instead of the default configuration since the EAP executes using the production configuration unless instructed otherwise by the user.
javax.naming.NameNotFoundException after a connection attempt. The JNDI names have been updated in order to rectify this issue.
build.properties file.
GWT - 1.4.62
Groovy 1.5.6
Spring 2.0.8
RichFaces 3.1.6
The following Seam JIRA issue fixes have been included within this Feature Pack release:
JBSEAM-3101: The example of a blog within Seam would generate a XML parsing error when it was launched in a browser. Correcting this issue has been achieved by modifying the code within the import.sql file.
JBSEAM-3090: The XSD for the web component namespace would incorrectly declare the servlet-session element. This element is now correctly declared.
JBSEAM-3078: New entities to a conversation would not be wrapped by the ServerConversationContext. The issue was fixed so that new entities would be wrapped appropriately.
JBSEAM-3071: There was an issue with Seam Mail that would create headers with new lines. To fix this, support has been added for line folding.
JBSEAM-3064: An AuthorizationException would occur when Load Testing because the method RuleBasedIdentity.hasPermission() would return false when it should have returned true. Fixing this issue has meant including Drools 4.0.7, including the synchronizeContext() method call that is within hasPermission() within the synchronized block and adding a synchronized block to the hasRole() method.
JBSEAM-3058: HTML and CSS sanitation filters for Seam Text would not work correctly. To fix this issue the SeamTextParser.Sanitizer has been backported. However because of this certain style values in plain HTML elements may no longer work.
JBSEAM-3053: The ID for a natural conversation was being initialized at the incorrect time, which would lead to exceptions. Correction of this issue has been undertaken by making sure that the ID is initilized at the correct time.
JBSEAM-3049: A javax.persistence.EntityNotFoundException error would be thrown when activating passivated entities that had been deleted. This has been corrected by using Hibernate to establish the entity class where possible, but to fall back to lesser methods when Hibernate is not an option.
JBSEAM-3027: The seasm-gen richfaces skin called sakura was not avaliable while still being a selectable option. This release fixes this issue by changing the theme to japanCherry.
JBSEAM-3003: Parameters within the UrlBuilder would not maintain correct insertion order. This has been corrected by allowing the UrlBuilder to maintain insertion order.
JBSEAM-2956: The example within Seam called seambay threw an exception when placing a bid on the camera. This has been corrected by initializing the natural conversation ID at the correct time.
icefaces in seam-gen
Groovy integration
groovybooking example
icefaces integration
icefaces example
Spring integration
spring example
portal portlet bridge integration
Google Web Kit integration
meldware libraries, which are required for the org.jboss.seam.mail.Meldware class.
The following is a list of unsupported Seam elements which have been removed from the Feature Pack:
Wiki example
JEE5 example
seam-jbas5 component
Container support other than for the EAP has been removed from the examples.
Hibernate: 3.2.4
Hibernate Annotations: 3.3.1
Hibernate-Commons Annotations: 3.0.0
Hibernate Entity Manager: 3.3.2
Hibernate Validator: 3.0.0
| Revision History | |||
|---|---|---|---|
| Revision 1.0 | |||
|
| |||