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.