Red Hat JBoss Web Framework Kit 2.7

2.7.0 Release Notes

Information about changes to JBoss Web Framework Kit

Red Hat Customer Content Services

Legal Notice

Copyright © 2015 Red Hat, Inc.
This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack Logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.

Abstract

These release notes contain important information related to this release of JBoss Web Framework Kit. New features, resolved issues and known issues of this product release are detailed here.

1. Red Hat JBoss Web Framework Kit 2.x End Of Life

Red Hat JBoss Web Framework Kit 2.x has a published end-of-life date of June 2015. For more information, see https://access.redhat.com/support/policy/updates/jboss_notes
JBoss Web Framework Kit has been the principal means by which Red Hat tested and supported popular open source web frameworks such as Apache Struts, Spring and Google Web Toolkit (GWT) running on Red Hat JBoss Enterprise Application Platform. Since the inception of JBoss Web Framework Kit, the industry has begun to move away from traditional server-side HTML-generating frameworks to ultra-rich HTML5 browser-optimized user experiences. In addition, some (previously) wildly popular open source web frameworks like Apache Struts have come to their community end of life. Furthermore, innovative frameworks like Seam have primarily been incorporated into the Java EE 6 specification to ensure ongoing support as part of an industry standard.
There are some components of JBoss Web Framework Kit that continue to be supported through other products in the Red Hat portfolio. For more information, see https://access.redhat.com/solutions/1314313 on the Red Hat Customer Portal.

2. Introduction to Red Hat JBoss Web Framework Kit

2.1. About Red Hat JBoss Web Framework Kit

Red Hat JBoss Web Framework Kit is a set of enterprise-ready versions of popular open source frameworks. Together, these frameworks provide a solution for developing light and rich Java-based web applications.
JBoss Web Framework Kit comprises enterprise distributions of JBoss community web application frameworks and tested third-party frameworks. These leading frameworks support fast and easy client-side and server-side application development and testing, with frameworks including RichFaces, jQuery, jQuery Mobile, Hibernate Search, Spring, and Arquillian.
The breadth of JBoss Web Framework Kit frameworks provides choice for Java application development. Each framework has been tested and certified for use in applications deployed to Red Hat JBoss Enterprise Application Platform, Red Hat JBoss Web Server, or Red Hat OpenShift JBoss EAP cartridge. Inclusion in JBoss Web Framework Kit ensures stable versions of frameworks are available over long-term enterprise product life cycles, with regular releases for fixes and nonintrusive feature updates. Further, Red Hat JBoss Developer Studio (an Eclipse-based development environment) provides integrated project templates, quickstarts and tooling for many of the JBoss Web Framework Kit frameworks.
For the complete list of the frameworks composing JBoss Web Framework Kit and the certified platform and framework configurations, see https://access.redhat.com/site/articles/112543 on the Red Hat Customer Portal.

2.2. About the JBoss Web Framework Kit Tiers

The frameworks composing JBoss Web Framework Kit are categorized in four distinct tiers. A description of each tier and the associated Red Hat support is detailed here.
Tier 1 - Included Components
These are components that are based wholly or partly on open source technologies that support broad collaboration and where Red Hat maintains a leadership role; as such Red Hat is able to support these components and provide upgrades and fixes under our standard support terms and conditions.
Tier 2 - Tested Frameworks
These are third-party frameworks where Red Hat does not have sufficient influence and does not provide upgrades and fixes under our standard support terms and conditions. Commercially reasonable support is provided by Red Hat Global Support Services for these frameworks.
Tier 3 - Frameworks in Tested Examples
These are third-party frameworks where Red Hat does not have sufficient influence and does not provide upgrades and fixes under our standard support terms and conditions. Red Hat supports the examples these frameworks are used in and the generic use cases that these examples intend to demonstrate.
Tier 4 - Confirmed Frameworks
These are third-party frameworks that do not receive any support from Red Hat, but Red Hat verifies that the frameworks run successfully on Red Hat JBoss Enterprise Application Platform. Frameworks and versions not listed here have not been explicitly tested and certified, and thus may be subject to support limitations.
For a list of JBoss Web Framework Kit frameworks by tier, see https://access.redhat.com/site/articles/112543 on the Red Hat Customer Portal.

2.3. About the JBoss Web Framework Kit Distribution

The frameworks composing JBoss Web Framework Kit are distributed from a range of sources and in a variety of formats:
  • The component frameworks are available from the Red Hat Customer Portal. They are distributed in two alternative formats: a binary for each framework or together as one Maven repository. In addition, the source code for each framework is provided for inspection.
  • The third party frameworks are not distributed by Red Hat and each must be obtained from its own source.
A number of defined Maven JBoss stacks are provided as part of the JBoss Web Framework Kit distribution. All of the BOMs defining the JBoss stacks are available in the Maven repository .zip file available to download from the Red Hat Customer Portal or from http://www.jboss.org/developer-materials/ on the JBoss Developer Framework website.
An extensive set of examples are also provided as part of the JBoss Web Framework Kit distribution:
  • TicketMonster is a moderately complex application demonstrating a number of the JBoss Web Framework Kit frameworks working together.
  • Quickstarts and Maven archeypes illustrate subsets of the JBoss Web Framework Kit frameworks used to create simple applications.
  • RichFaces, Snowdrop and Seam demonstrations showcase the power of each framework in web application development.
All of these examples are available from the Red Hat Customer Portal, with TicketMonster, the quickstarts, and the Maven archetypes also available from http://www.jboss.org/developer-materials/ on the JBoss Developer Framework website.

3. About this Release

JBoss Web Framework Kit 2.7.0 is an update to JBoss Web Framework Kit 2.6.x. The update has a number of purposes:
  • It supports updated versions of supported platforms.
  • It contains updates to JBoss Web Framework Kit components.
  • It supports updated versions of tested frameworks.
  • It contains updated quickstarts and showcase examples, and consequently supports newer versions of frameworks in tested examples.
  • It resolves issues identified in earlier versions of JBoss Web Framework Kit components, quickstarts and showcase examples.

4. Updated Supported Components and Configurations

This release of JBoss Web Framework Kit includes updated versions of components and support for updated versions of platforms and third-party frameworks as detailed here. For a complete list of all certified platform and framework configurations and supported web browsers for this release, together with details of Red Hat support for each certified configuration, see https://access.redhat.com/site/articles/112543 on the Red Hat Customer Portal.

Updated Supported Platforms
  • Red Hat JBoss Enterprise Application Platform 6.3.2
  • Red Hat JBoss Web Server 2.1.0
  • OpenShift JBoss EAP Cartridge 6.3.2
Updated JBoss Web Framework Kit Components
  • Hibernate Search 4.4.4.Final-redhat-wfk-1
  • RichFaces 4.5.2.Final-redhat-1
  • Seam 2.3.5.Final-redhat-1
  • Snowdrop 3.1.1.Final-redhat-1

    Important

    Red Hat JBoss Enterprise Application Platform 6.0.x contains several outdated static modules and the following frameworks must be used with JBoss EAP 6.1 and later:
    • RichFaces 4.5, due to outdated jsf-api and jsf-impl modules
    • Seam 2.3, due to an outdated infinispan module
    This applies to use of the frameworks in your own applications and use of the distributed quickstarts and demos.

    Important

    Red Hat continues to distribute and support Hibernate Search for use with Red Hat JBoss Enterprise Application Platform. Future Hibernate Search framework and documentation releases will be part of JBoss EAP releases. For more information, see https://access.redhat.com/solutions/1314313 on the Red Hat Customer Portal.

    Warning

    RichFaces 4.x and Snowdrop are deprecated from the release of JBoss Web Framework Kit 2.7.0. This means that no new features will be introduced to the RichFaces 4.x or Snowdrop frameworks in JBoss Web Framework Kit 2.7.0 or later. As tier 1 frameworks, Red Hat continues to support RichFaces 4.x and Snowdrop and provide fixes under our standard support terms and conditions. For more information about the Red Hat support policy, see https://access.redhat.com/support/policy/updates/jboss_notes/.

    Warning

    Seam 2.3 is deprecated from the release of JBoss Web Framework Kit 2.6.0. This means that no new features will be introduced to the Seam 2.3 framework in JBoss Web Framework Kit 2.6.0 or later. As a tier 1 framework, Red Hat continues to support Seam 2.3 and provide fixes under our standard support terms and conditions. For more information about the Red Hat support policy, see https://access.redhat.com/support/policy/updates/jboss_notes/.
Updated Tested Frameworks
  • Arquillian 1.1.5.Final
  • DeltaSpike 1.2.1
  • Spring 3.2.13.RELEASE, 4.0.9.RELEASE and 4.1.4.RELEASE
  • Spring Roo 1.3.0.RELEASE
  • Spring Security 3.2.5.RELEASE
  • Spring Web Flow 2.4.1.RELEASE

    Important

    DeltaSpike modules are supported at different levels as follows:
    • Fully supported modules are Core, JPA, Security, Bean Validation, and Servlet.
    • Technology Preview modules are JSF, Data, Partial-Bean, and Scheduler.

    Important

    • Support of Spring 4 as a tested framework is limited to the features supported by Red Hat JBoss Enterprise Application Platform. Specifically support is not provided for the new features in Spring 4 related to Java SE 8 and Java EE 7.
    • Red Hat continues to test Spring for use with Red Hat JBoss Enterprise Application Platform. Future Spring testing and support will be part of JBoss EAP releases. For more information, see https://access.redhat.com/solutions/1314313 on the Red Hat Customer Portal.
Updated Frameworks in Tested Examples
  • Apache Cordova 3.5.1
  • jQuery Validate 1.13.1
  • Modernizr 2.8.3
Updated Confirmed Frameworks
  • Grails 2.4.4
  • PrimeFaces 5.1
  • Struts 2 2.3.20

5. New Features

This release of JBoss Web Framework Kit includes new features to enhance and extend its functionality as detailed here.
WFK2-733
A new version of the Snowdrop example Sportsclub is available. This new example demonstrates how to build a Spring application for deployment on JBoss EAP without the previously needed Snowdrop support. If you are using Snowdrop, this example and supporting documentation provides a demonstration of how to migrate your applications off Snowdrop. The new Sportsclub example can be found in the jboss-wfk-2.7.0-snowdropless-demo.zip file.
WFK2-729
Autocomplete functionality has been added to the rich:select component. This provides RichFaces users with the capability to do object-based autocomplete features, just as for the RichFaces 3 rich:suggestionbox component. Text-based autocomplete is still provided through the rich:autocomplete component.
WFK2-635
The contacts-mobile-basic quickstart did not accept non-US phone numbers when adding or editing a contact, with the message "Please use a standard US formats. And remember the area code and prefix may not start with 1." The quickstart functionality has been extended to allow and validate international phone numbers. A new international phone number jQuery library was included to provide the needed support.
WFK2-582
The rich:push component now leverages websockets where available and otherwise falls back to long-polling. Websockets are available in Red Hat JBoss Enterprise Application Platform 6.3 and later but they must be explicitly enabled in the server configuration as detailed in the JBoss EAP documentation.
WFK2-560
A subset of the JBoss Web Framework Kit Included Components and Tested Frameworks are certified with Java Runtime Environment 8 as follows:
  • Arquillian
  • Arquillian Drone
  • Arquillian Graphene
  • DeltaSpike
  • Hibernate Search
  • RichFaces
  • Seam 2
  • Spring - versions 3.2.x, 4.0.x, and 4.1.x
Note that the certification is limited to Red Hat JBoss Enterprise Application Platform 6.3 and Oracle Java Standard Edition 8.
WFK2-152
Spring 4 was supported for use with Red Hat JBoss Enterprise Application Platform 6.3.x in the last JBoss Web Framework Kit release but not all features were supported, including WebSocket protocol. As of this JBoss Web Framework Kit release, the WebSocket protocol is supported for use.
WFK2-108
Developer experience materials are available freely from http://www.jboss.org/developer-materials on the JBoss Developer website, in addition to the Red Hat Customer Portal for subscription holders. Developer materials include quickstarts, archetypes, the TicketMonster extended example, and BOMs.

6. Resolved Issues

The issues listed here have been resolved in this release of JBoss Web Framework Kit.

DeltaSpike

WFK2-607
Any archive which bundles the DeltaSpike Scheduler Implementation module and does not bundle the Quartz library failed to deploy on Red Hat JBoss Enterprise Application Platform 6.2.x. This was caused by an issue in Weld which caused a deployment failure if an archive contains a class that has a missing dependency in a type argument. JBoss EAP 6.3.0 has been upgraded to Weld 1.1.22.Final, which resolves the issue.

Hibernate Search

WFK2-740
An issue occurred when multiple threads applied changes to the database without using a JTA transaction or these operations affected entities which were directly, indexed or included in a relation with another indexed entity (for example via a relation marked with the @ContainedIn annotation). Some of the changes that would normally be scheduled by the indexing engine were discarded before being applied to the index, resulting in the index getting out of sync with the data stored in the database. The collection used to schedule the indexing operation was replaced with a different collection implementation which is thread-safe. As a result, indexing operations are not lost and get applied to the index so the index state is maintained in sync with the database state as expected.

RichFaces

WFK2-869
The RichFaces simple archetype, version 2.6.0.Final, was not updated to use the JBoss Web Framework Kit BOM 2.6.0-redhat-1, continuing to reference the BOM 2.5.0-redhat-1 and old artifacts. For JBoss Web Framework Kit 2.7, the RichFaces simple archetype has been correctly updated to the BOM 2.7.0-redhat-1.
WFK2-781
Selecting an item in a rich:select component, then rendering that select component in an ajax update resulted in the selected item of the component not being highlighted when the dropdown list was expanded. The rich:select component has been fixed to correctly highlight the selected item after an ajax update.
WFK2-730
In portal environments the rich:fileupload component broke the form action. The rich:fileupload component has been replaced with an new implementation that does not break the form action.
WFK2-712
An error occurred when using the RichFaces Photoalbum example. When a user refreshed the index.html page of the example, an error message displayed and the Photoalbum stopped working. This was caused by the rich:tree component incorrectly binding to a SessionScoped backing bean via its binding attribute. The example has been updated to not use a bound component.

Seam 2

WFK2-851
There was an error in the JBoss AS XML schema file, jboss-deployment-structure-1_0.xsd. As a consequence, Red Hat JBoss Developer Studio displayed the following project error for imported Seam examples:
Attribute 'name' is not allowed to appear in element 'sub-deployment'
Schema in Seam examples must be upgraded to version 1.1 to avoid validation errors with schema version 1.0.

Spring

WFK2-816
Sportsclub reservation-webflow application demonstration contained the wrong relative path to the favicon.png file, resulting in the image not being found for the generated web pages. This has been resolved by adding ${request.contextPath} to the referenced path links.
WFK2-806
README.md instructions in the Snowdrop Sportsclub example described an upstream setup for Maven. Following these upstream instructions could result in the example not building. The instructions have been fixed to detail the JBoss Web Framework Kit setup for Maven.
WFK2-692
Earlier versions of the Snowdrop Installer were dependent on the xmlns in Standalone.xml file. This fix removes the dependency, allowing the Installer to work without modification on future versions of EAP.
WFK2-673
In the Spring Sportsclub reservations-weblfow submodule, you could not change the date and time when creating or editing reservations. This has been fixed by wrapping the calendar component in a form tag, enabling the date and time to be changed when creating or editing reservations.
WFK2-512
The Snowdrop installer README.md file did not describe how to integrate the Red Hat JBoss Web Framework Kit Maven repository. This information is now included.
WFK2-435
The Spring RESTeasy quickstart did not run with Spring 4. This was because the resteasy-spring.jar used Spring 3.0.3 and its deprecate method org.springframework.web.context.ContextLoaderListener.createContextLoader() which was removed in Spring 4. Red Hat JBoss Enterprise Application Platform 6.2.2 and 6.3.0 were upgraded to RESTeasy Spring integration 2.3.8, resolving the incompatibilities and enabling the Spring RESTeasy quickstart to be successfully run with Spring 4.

TicketMonster

WFK2-717
TicketMonster images are stored on an external service and are loaded using HTTPS requests, however images URLs stored in database have HTTP prefixes. TicketMonster HTTP requests for resources are redirected to HTTPS URLs. This is why TicketMonster caches redirection pages. This is resolved by replacing the HTTP protocol with HTTPS for MediaItems in the import.sql file.
WFK2-711
An error occurred when generating an administration layer in the TicketMonster example using Forge 2 in Red Hat JBoss Developer Studio. This was because the Forge 2 plug-in used the ~/.m2/settings.xml file instead of the Eclipse/m2e/settings.xml file. This issue has subsequently been fixed in Forge 2 and an error no longer occurs when generating an administration layer in the TicketMonster example using Forge 2 in JBoss Developer Studio 8.

Quickstarts

WFK2-749
An error was thrown when Maven projects using m2e-wro4j 1.0.2 had their minify profiles activated. The error was caused by the wro4j-maven-plugin using an incompatible version of wro4j plug-in. The plug-in has been removed in this release so these projects build as expected.

7. Known Issues

The issues listed here are unresolved in this release of JBoss Web Framework Kit.

Arquillian

WFK2-871
Arquillian Drone used in JBoss Web Framework Kit does not support the latest Selenium version, using Selenium 2.43.1 instead. This version of Selenium is not compatible with Google Chrome 39. To work around this issue, use Google Chrome 36 which is known to work with Arquillian-based functional tests.
WFK2-642
An error occurs when running Seam functional tests that implement the Arquillian Open Service Gateway initiative artifacts defined in the org.jboss.arquillian.osgi:arquillian-osgi-parent:1.0.3.Final file. This file is stored in the org.jboss.osgi.spi:jbosgi-spi:3.2.0.CR1 repository, but when running functional tests, Maven attempts to use the pom file for the org.jboss.osgi.spi:jbosgi-spi:3.2.0.CR1 repository instead. To work around this, the settings.xml file must reference the jboss.org repository.
WFK2-381
Attempting to use a @ServerTask configuration in the Arquillian adaptor for Red Hat JBoss Enterprise Application Platform results in an exception. The operation does not reload to update the configuration even after applying management operation(s). To workaround the issue, users must modify Red Hat JBoss Enterprise Application Platform using Red Hat JBoss Command Line Interface to recognize updates.
WFK2-231
Arquillian Graphene guards are not functional with the AngularJS JavaScript library, causing exceptions in AngularJS applications. This is because AngularJS stores a reference to XMLHttpRequest objects when a script is loaded, causing Arquillian Graphene to fail when attempting to rewrite those objects. No workaround for this issue exists. Red Hat recommends using waits instead of guards where necessary.
WFK2-61
The @ArquillianResource URL injection injects an incorrect URL if the deployed package name contains a full stop ('.'). The only workaround currently known for this issue is to rename the deployed package so that its name does not contain any full stops.

Google Web Toolkit

WFK2-329
Workers compiling Google Web Toolkit applications communicate via sockets with a port number that is forbidden on OpenShift. Consequently, compilation of Google Web Toolkit applications on OpenShift fails with the following error message:
[ERROR] Unable to create socket 
java.net.BindException: Permission denied
To work around the issue, create the workers using the ThreadedPermutationWorkerFactory.java class instead of the default ExternalPermutationWorkerFactory.java class. This can be achieved by setting the following extra JVM argument in the settings of the GWT Maven plug-in:
<plugin> 
  <groupId>org.codehaus.mojo</groupId> 
  <artifactId>gwt-maven-plugin</artifactId> 
  ... 
  <configuration>
    <extraJvmArgs>-Dgwt.jjs.permutationWorkerFactory=com.google.gwt.dev.ThreadedPermutationWorkerFactory</extraJvmArgs> 
    ... 
  </configuration> 
  ... 
</plugin>
With this option set, workers are created in new threads, do not use any sockets, and compilation of Google Web Toolkit applications on OpenShift can be performed successfully.
WFK2-37
Google Web Toolkit attempts to load pre-compiled module archives (.gwtar files) to increase performance. Consequently, building Google Web Toolkit examples shipped with this release fails with the IBM implementations of the Java Developement Kit (both 1.6 and 1.7). To work around the issue, use the -Dgwt.usearchives=false parameter with gwt-maven-plugin to disable loading of the pre-compiled archives.

Grails

WFK2-65
OSGi is not enabled in Red Hat JBoss Enterprise Application Platform 6, and artifacts produced by Grails 1.3.9 miss a Package-Import of javax.naming in the bundle. To work around the issue, disable adding of OSGi headers while packaging your Grails applications by adding the following configuration into the BuildConfig.groovy configuration file:
grails.project.war.osgi.headers = false

jQuery Mobile

WFK2-679
jQuery Mobile 1.4 is not backwards compatible. Because of this, applications using older versions of jQuery Mobile must be modified to use jQuery 1.4. To upgrade to jQuery Mobile 1.4, see the jQuery Mobile 1.4 Upgrade Guide available at http://jquerymobile.com/upgrade-guide/1.4/.

RichFaces

The rich:fileUpload component does not work in applications viewed with Internet Explorer 9. This RichFaces component does work with later versions of Internet Explorer. There is no workaround for use of the rich:fileUpload component in applications at this time.
WFK2-872
The RichFaces distribution .zip file contains VDLdoc for components in the a4j namespace but it is missing documentation for components in the rich namespace. To work around this issue, use the community VLDdoc available at http://docs.jboss.org/richfaces/4.5.X/4.5.2.Final/vdldoc/.
WFK2-864
The rowclick event of the rich:dataTable is not recognized as a valid server-side event during an ajax postback. To work around this issue, use the selectionchange event instead of the rowclick event.
WFK2-744
When a JSF form is submitted using a h:commandLink, the onsubmit listener of the placeholder component is not triggered. This behaviour can interfere with the enforcement of component validations. The problem originates in Mojarra and will be addressed in Red Hat JBoss Enterprise Application Platform 6.4. In the interim, a workaround for this issue is to use the a4j:commandLink instead of the h:commandLink.
WFK2-145
When using Spring WebFlow 2.3 with Spring 3.x and RichFaces 4, an extra bean service must be created to resolve RichFace resources. This bean is not automatically included as part of faces:resources, causing a 404 error to occur when a CSS file is requested. To work around this issue, change the order of the flowMapping so that RichFaces has higher priority than the user-generated flow (the lower number gets higher priority), and add the following bean to your application:
<bean name="richfacesResourceHandler" class="org.springframework.faces.webflow.JsfResourceRequestHandler" /> 

<bean class="org.springframework.web.servlet.handler.SimpleUrlHandlerMapping"> 
  <property name="order" value="1" /> 
  <property name="mappings"> 
    <value> 
       /rfRes/**=richfacesResourceHandler 
    </value> 
  </property> 
</bean>
After this configuration change, the request for the CSS file loads as expected.

Seam 2

WFK2-725
XML validation in Red Hat JBoss Developer Studio for a components.xml file containing custom Seam components which define their namespace using the @Namespace annotation results in an error message such as the following:
cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'pay:payment-home'.	components.xml
There is no workaround at this time.
WFK2-646
A NullPointerException from Seam's SubscriptionRequest component is intermittently triggered when a subscription request is issued by a client to a JMS topic shortly after initiating an endpoint connection. This is caused by non-thread-safe behaviour of a built-in Seam component resulting in race conditions arising. To work around this, eliminate the race condition by forcing the topicConnection component to be created during application startup. This is achieved by including the following component in the application:
import org.jboss.seam.annotations.*; 
import org.jboss.seam.ScopeType; 
import javax.jms.TopicConnection; 

@Name("topicConnectionStartup") 
@Startup 
@Scope(ScopeType.APPLICATION) 
public class TopicConnectionStartup { 
    @In(value="org.jboss.seam.jms.topicConnection", create=true) 
    private TopicConnection topicConnection; 

    @Create 
    public void init() { 
        topicConnection.toString(); // arbitrary call to invoke injection of topicConnection 
    } 
}
WFK2-615
Seam does not unlock conversations as expected after they have been terminated with an @End method. This can cause problems in specific cases of concurrent requests to the same conversation, which leads to exceptions including ConcurrentRequestTimeoutException or ConcurrentModificationException. There is no workaround at this time.
WFK2-493
When sending Ajax requests to an expired session, Seam will not propagate FacesMessage. As a result, error messages are not displayed when an exception is thrown in Ajax. You can implement an Ajax exception handler by adding the following code in the faces-config.xml file:
<factory> 
    <exception-handler-factory>
        your_full_ajax_exception_handler
    </exception-handler-factory> 
</factory>
WFK2-229
The Seam user interface example throws an error related to the JPA programming interface when imported to Red Hat JBoss Developer Studio. The error occurs because JPA programming interface validation rules wrongly parse the @ElementCollection annotation, resulting in errors wrongly being reporting. The errors can be safely ignored.
WFK2-96
The UIDataTable component (the <rich:dataTable> element) shipped with RichFaces 4 does not extend the JSF UIData class. As a consequence, rendering of Seam components annotated with @DataModel and @DataModelSelection inside a UIDataTable does not work as expected. As a workaround, use the JSF DataTable (the <h:dataTable> element) instead of the Richfaces UIDataTable.
WFK2-95
When locale-config configuration is used in a Seam application, the following error message is shown in the server container log:
SEVERE [javax.faces] (MSC service thread 1-2) Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory. Attempting to find backup.
As a consequence, locale-config configuration is not taken into account in the application. As a workaround, use com.sun.faces.config.ConfigureListener configuration in the application's web.xml file. As a result of the workaround, the locale configuration works as expected.
WFK2-90
The Seamspace example fails with a NullPointerException while submitting a new blog entry on the IBM virtual machine. This issue is caused by a defect in the IBM virtual machine. The fix for this issue has been deferred until the IBM virtual machine is fixed.
WFK2-86
When Trinidad tag selectOneChoice is used on an entity that has a @OneToMany relationship with another entity, the relationship is broken because the entity does not get the relationship key. As a consequence, you cannot perform edit and save operations on the disc.xhtml file due to the following exception:
java.lang.NumberFormatException: For input string: "org.jboss.seam.example.seamdiscs.model.Band@3dd00249"
To work around this issue, replace the <tr:selectOneChoice> tag in the disc.xhtml file with the standard JavaServer Faces tag <h:selectOneMenu>.

Spring

WFK2-675
An error occurs in the Spring Sportsclub reservations webflow submodule. If you search for a reservation, click on it, edit it, save it and go back to Search page, the detailed information is not refreshed and does not display changes. The workaround is to select another reservation and then back to see the edited reservation updated.
WFK2-672
In the Spring Sportsclub reservations-webflow submodule, when Creating or Editing a reservation, there is an Available Equipment table with multiple pages. From the Available Equipment table, page 1, if you navigate to another page (page 2 or page 3) it does not allow you to return back to page 1. To work around this, you must select Create or Edit to effectively refresh the page and navigate back to page 1 of the table.
WFK2-671
In the Spring Sportsclub reservations-webflow submodule, when Creating or Editing a reservation, there is a Select Account table with multiple pages. From the Select Account table, page 1, if you navigate to another page (page 2 or page 3) it does not allow you to return back to page 1. To work around this, you must select Create or Edit to effectively refresh the page and navigate back to page 1 of the table.
WFK2-601
The default Spring servlet ("/") cannot be overridden without using the web.xml file. This occurs when users attempt to to bootstrap Spring WebMVC without the XML configuration files.The url pattern "/" should override default servlet mapping, but instead returns a 404 error.
WFK2-75
Some Spring libraries have optional dependencies on other libraries that are not present in the org.springframework.spring JBoss module by default (e.g. the quartz library). As a consequence, applications that depend on Spring libraries installed as JBoss modules cannot be deployed if the applications also require optional Spring dependencies. You can use one of the following workarounds for this issue:
  1. Do not depend on Spring libraries installed as JBoss modules; build the project with all the required JAR files.
  2. Add the optional dependencies into the org.springframework.spring module. Example of a module.xml file is as follows:
    <module xmlns="urn:jboss:module:1.1" name="org.springframework.spring"> 
      <resources> 
        <resource-root path="com.springsource.org.aopalliance-1.0.0.jar" /> 
        ... 
        <resource-root path="spring-expression-3.2.4.RELEASE.jar" /> 
        <resource-root path="quartz-2.2.1.jar" /> 
        <resource-root path="bsh-2.0b5.jar" /> 
      </resources> 
      <dependencies> 
        <module name="org.apache.commons.logging"/> 
        <module name="javaee.api"/> 
        <module name="org.jboss.vfs"/> 
      </dependencies> 
    </module>

Struts

WFK2-64 WFK2-63
The JSF integration in the Struts 1 and 2 Showcase applications is not functional with Red Hat JBoss Enterprise Application Platform 6. To work around this issue, override the default JSF implementation by adding the following configuration into the web.xml file of the application:
<context-param> 
   <param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name> 
   <param-value>true</param-value> 
</context-param>

TicketMonster

WFK2-230
For TicketMonster imported into Red Hat JBoss Developer Studio, when running the admin_layer.fsh script with JBoss Forge, the patches in the TicketMonster directory are not applied. This is because the script does not apply the patches automatically on the TicketMonster sources.
To work around this issue, apply the patches manually as described here. In Red Hat JBoss Developer Studio, in the Project Explorer view right-click on the project and click Team > Apply Patch. Locate the patch file in the Workspace, select it and click Next. Both the patches are located in the ticket-monster2.7.0.Final/demo/patches directory. Select the admin_layer_functional.patch and admin_layer_graphics.patch files to apply the functional and stylistic changes, then click Next. From the menu, select to apply the patches on the 'ticket-monster' project in the workspace and click Finish to apply the patches.

8. Apply this Release

JBoss Web Framework Kit 2.7.0 Maven repository, examples and quickstarts are packaged and distributed individually. This individualized distribution enables you to customize your JBoss Web Framework Kit 2.7.0 update based on the frameworks you use and functional requirements you need.
  • To use the JBoss Web Framework Kit 2.7.0 Maven repository, use the Maven repository .zip file available from the Red Hat Customer Portal.
  • To use the JBoss Web Framework Kit 2.7.0 JBoss stacks, use the Maven repository .zip file available from the Red Hat Customer Portal or download individual BOMs from the JBoss Developer website.
  • To use the JBoss Web Framework Kit 2.7.0 component examples, use the framework-specific demo .zip files available from the Red Hat Customer Portal.
  • To use the JBoss Web Framework Kit 2.7.0 quickstarts, use the quickstarts.zip file available from the Red Hat Customer Portal or download individual quickstarts from the JBoss Developer website. Alternatively, a number of the quickstarts are also provided in Red Hat JBoss Developer Studio.
  • To upgrade a supported platform or tested framework, see the download and install instructions for the particular product.
For more information see the Red Hat JBoss Web Framework Kit 2.7 Install document available on the Red Hat Customer Portal.

A. Revision History

Revision History
Revision 2.7.0-1Thu Jan 22 2015Michelle Murray
Generated for WFK 2.7 release