Red Hat JBoss Web Framework Kit 2.2 2.2.0 Release Notes

Red Hat Documentat ion Team

Red Hat JBoss Web Framework Kit2.22.2.0 Release Notes

for use with JBoss Web Framework KitEdit ion 2.2.0

Red Hat JBoss Web Framework Kit 2.2 2.2.0 Release Notes

for use with JBoss Web Framework KitEdit ion 2.2.0

Red Hat Documentation TeamRed Hat Engineering Content Services

Legal Notice

Copyright © 2013 Red Hat, Inc.

This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0Unported License. If you distribute this document, o r a modified version o f it, you must provideattribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all RedHat trademarks must be removed.

Red Hat, as the licensor o f this document, waives the right to enforce, and agrees not to assert,Section 4d o f CC-BY-SA to the fullest extent permitted by applicable law.

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the InfinityLogo, and RHCE are trademarks o f Red Hat, Inc., registered in the United States and o thercountries.

Linux ® is the registered trademark o f Linus Torvalds in the United States and o ther countries.

Java ® is a registered trademark o f Oracle and/or its affiliates.

XFS ® is a trademark o f Silicon Graphics International Corp. or its subsidiaries in the UnitedStates and/or o ther countries.

MySQL ® is a registered trademark o f MySQL AB in the United States, the European Union andother countries.

Node.js ® is an o fficial trademark o f Joyent. Red Hat Software Collections is not fo rmallyrelated to or endorsed by the o fficial Joyent Node.js open source or commercial pro ject.

The OpenStack ® Word Mark and OpenStack Logo are either registered trademarks/servicemarks or trademarks/service marks o f the OpenStack Foundation, in the United States and o thercountries 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 o ther trademarks are the property o f their respective owners.

AbstractThese release notes contain important information related to JBoss Web Framework Kit 2.2.0 .You should read these release notes in their entirety before installing the JBoss WebFramework Kit 2.2.0 .

http://creativecommons.org/licenses/by-sa/3.0/

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents

Preface1. Do cument Co nventio ns1.1. Typ o g rap hic Co nventio ns1.2. Pull-q uo te Co nventio ns1.3. No tes and Warning s

2. Getting Help and G iving Feed b ack2.1. Do Yo u Need Help ?2.2. We Need Feed b ack!

Chapt er 1 . Int roduct ion1.1. Overview

Chapt er 2 . Component s2.1. Inc lud ed Co mp o nents2.2. Tested Framewo rks2.3. Co nfirmed Framewo rks2.4. JBo ss Enterp rise Web Server Co mp atib il i ty

Chapt er 3. T echnology PreviewsTo rq ueBo xErrai 2DeltaSp ike 0 .3-incub ating

Chapt er 4 . Inst allat ion Not es4.1. ZIP Packag es Do wnlo ad ab le fro m Red Hat Custo mer Po rtal4.2. JBo ss Web Framewo rk Kit Maven Rep o sito ry Installatio n

Chapt er 5. Enhancement s

Chapt er 6 . Fixed Issues

Chapt er 7 . Known Issues

Chapt er 8 . Product Support and License Websit e Links

Revision Hist ory

22234445

66

778

1011

1 3131314

1 51516

1 7

1 8

2 3

37

38

T able of Cont ent s

1

Preface

1. Document Convent ions

This manual uses several conventions to highlight certain words and phrases and draw attention tospecific pieces of information.

1.1. T ypographic Convent ions

Four typographic conventions are used to call attention to specific words and phrases. Theseconventions, and the circumstances they apply to, are as follows.

Mono-spaced Bold

Used to highlight system input, including shell commands, file names and paths. Also used tohighlight keys and key combinations. For example:

To see the contents of the file my_next_bestselling_novel in your currentworking directory, enter the cat my_next_bestselling_novel command at theshell prompt and press Enter to execute the command.

The above includes a file name, a shell command and a key, all presented in mono-spaced bold andall distinguishable thanks to context.

Key combinations can be distinguished from an individual key by the plus sign that connects eachpart of a key combination. For example:

Press Enter to execute the command.

Press Ctrl+Alt+F2 to switch to a virtual terminal.

The first example highlights a particular key to press. The second example highlights a keycombination: a set of three keys pressed simultaneously.

If source code is discussed, class names, methods, functions, variable names and returned valuesmentioned within a paragraph will be presented as above, in mono-spaced bold . For example:

File-related classes include filesystem for file systems, file for files, and dir fordirectories. Each class has its own associated set of permissions.

Proport ional Bold

This denotes words or phrases encountered on a system, including application names; dialog-boxtext; labeled buttons; check-box and radio-button labels; menu titles and submenu titles. Forexample:

Choose System → Preferences → Mouse from the main menu bar to launchMouse Preferences . In the Buttons tab, select the Left-handed mouse checkbox and click Close to switch the primary mouse button from the left to the right(making the mouse suitable for use in the left hand).

To insert a special character into a gedit file, choose Applicat ions →Accessories → Character Map from the main menu bar. Next, choose Search →Find… from the Character Map menu bar, type the name of the character in the Search field and click Next. The character you sought will be highlighted in the

Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es

2

Character Table. Double-click this highlighted character to place it in the Text to copy field and then click the Copy button. Now switch back to your documentand choose Edit → Paste from the gedit menu bar.

The above text includes application names; system-wide menu names and items; application-specificmenu names; and buttons and text found within a GUI interface, all presented in proportional boldand all distinguishable by context.

Mono-spaced Bold Italic or Proportional Bold Italic

Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable orvariable text. Italics denotes text you do not input literally or displayed text that changes dependingon circumstance. For example:

To connect to a remote machine using ssh, type ssh [email protected] at ashell prompt. If the remote machine is example.com and your username on thatmachine is john, type ssh [email protected].

The mount -o remount file-system command remounts the named file system.For example, to remount the /home file system, the command is mount -o remount /home.

To see the version of a currently installed package, use the rpm -q packagecommand. It will return a result as follows: package-version-release.

Note the words in bold italics above: username, domain.name, file-system, package, version andrelease. Each word is a placeholder, either for text you enter when issuing a command or for textdisplayed by the system.

Aside from standard usage for presenting the title of a work, italics denotes the first use of a new andimportant term. For example:

Publican is a DocBook publishing system.

1.2. Pull-quote Convent ions

Terminal output and source code listings are set off visually from the surrounding text.

Output sent to a terminal is set in mono-spaced roman and presented thus:

books Desktop documentation drafts mss photos stuff svnbooks_tests Desktop1 downloads images notes scripts svgs

Source-code listings are also set in mono-spaced roman but add syntax highlighting as follows:

static int kvm_vm_ioctl_deassign_device(struct kvm *kvm, struct kvm_assigned_pci_dev *assigned_dev){ int r = 0; struct kvm_assigned_dev_kernel *match;

mutex_lock(&kvm->lock);

match = kvm_find_assigned_dev(&kvm->arch.assigned_dev_head, assigned_dev->assigned_dev_id); if (!match) { printk(KERN_INFO "%s: device hasn't been assigned

Preface

3

before, " "so cannot be deassigned\n", __func__); r = -EINVAL; goto out; }

kvm_deassign_device(kvm, match);

kvm_free_assigned_device(kvm, match);

out: mutex_unlock(&kvm->lock); return r;}

1.3. Notes and Warnings

Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.

Note

Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note shouldhave no negative consequences, but you might miss out on a trick that makes your life easier.

Important

Important boxes detail things that are easily missed: configuration changes that only apply tothe current session, or services that need restarting before an update will apply. Ignoring abox labeled “ Important” will not cause data loss but may cause irritation and frustration.

Warning

Warnings should not be ignored. Ignoring warnings will most likely cause data loss.

2. Get t ing Help and Giving Feedback

2.1. Do You Need Help?

If you experience difficulty with a procedure described in this documentation, visit the Red HatCustomer Portal at http://access.redhat.com. Through the customer portal, you can:

search or browse through a knowledgebase of technical support articles about Red Hat products.

submit a support case to Red Hat Global Support Services (GSS).

access other product documentation.


4

http://access.redhat.com

Red Hat also hosts a large number of electronic mailing lists for discussion of Red Hat software andtechnology. You can find a list of publicly available mailing lists athttps://www.redhat.com/mailman/listinfo. Click on the name of any mailing list to subscribe to that listor to access the list archives.

2.2. We Need Feedback!

If you find a typographical error in this manual, or if you have thought of a way to make this manualbetter, we would love to hear from you! Please submit a report in Bugzilla: http://bugzilla.redhat.com/against the product JBoss Web Framework Kit .

When submitting a bug report, be sure to mention the manual's identifier: 2.2.0_Release_Notes

If you have a suggestion for improving the documentation, try to be as specific as possible whendescribing it. If you have found an error, please include the section number and some of thesurrounding text so we can find it easily.

Preface

5

https://www.redhat.com/mailman/listinfo

http://bugzilla.redhat.com/

Chapter 1. Introduction

These release notes contain important information related to JBoss Web Framework Kit 2.2.0. Newfeatures, installation procedures, and known issues are addressed here.

1.1. Overview

JBoss Web Framework Kit combines popular open source web frameworks into a single solution forJava applications. The JBoss Web Framework Kit subscription is already included with JBossEnterprise Application Platform.

Certification

Red Hat Quality Engineering uses an extensive set of tests to validate against a specific set ofarchitectural components in our application stack (operating system, database driver,database, and JVM). The full list of certified environments is available fromhttp://www.jboss.com/products/platforms/application/supportedconfigurations/.

This certification applies only to the specific component versions listed under Chapter 2,Components.


6

http://www.jboss.com/products/platforms/application/supportedconfigurations/

Chapter 2. Components

This chapter details the specific components included in JBoss Web Framework Kit, as well as thespecific components that are certified for use with JBoss Web Framework Kit.

This release of JBoss Web Framework Kit is certified for use with:

JBoss Enterprise Application Platform 6.

Important

Support for using JBoss Web Framework Kit with the platform listed is subject to compliancewith the certified or compatible configurations for each of those platforms. Ensure that yourproducts are supported by complying with the specifications listed athttp://www.jboss.com/products/platforms/application/supportedconfigurations/.

Important

Examples included with this release of JBoss Web Framework Kit may contain componentswhich are not certified or supported. These components were present in the original versionand are preserved for consistent functionality. For an authoritative list of supported andcertified components, please consult Section 2.1, “ Included Components” of these ReleaseNotes.

2.1. Included Components

Included components are JBoss-owned frameworks where JBoss controls the upstream project andcan guarantee bug-fixes and patches.

Errai 2.2.0.Final

Errai is a framework and tool set that leverages the GWT compiler for the building of webapplications.

Hibernate Search 4 .2.0.Final

Hibernate Search brings the power of full text search engines to the persistence domainmodel by combining Hibernate Core with the capabilities of the Apache Lucene™ searchengine.

RichFaces 4 .3.1.Final

RichFaces is a rich component library for JavaServer Faces (JSF) and an advancedframework for easily integrating AJAX capabilities into business application development.

Seam 2.3.1.Final

Seam is a powerful open source development platform for building rich Internetapplications in Java. Seam integrates technologies such as Asynchronous JavaScript andXML (AJAX), JavaServer Faces (JSF), Java Persistence API (JPA) and Enterprise JavaBeans (EJB).

Chapt er 2 . Component s

7


Snowdrop 2.0.5.Final

Snowdrop is a utilities package that provides JBoss Enterprise Platform-specific extensionsfor the Spring framework.

Snowdrop Sportsclub Example

The Sportsclub application provides a real-world-inspired example of integrating Springwith the JBoss Enterprise Platforms.

TorqueBox 2.3.0

TorqueBox is built on top of the JBoss Application Server and delivers a platform for Rubyapplications.

TicketMonster Example

The TicketMonster example showcases how to create a modern web application configuredfor mobile and desktop interactoin.

2.2. Tested Frameworks

Tested frameworks are third party frameworks where JBoss does not control the upstream project.Frameworks in this category are supported by the JBoss team, but upstream bug-fixes and patchesare not provided.

Apache St ruts 1.3.10

Struts provides an open source framework useful in building web applications with JavaServlet and JavaServer Pages (JSP) technology. This framework encourages applicationarchitectures based on the Model-View-Controller (MVC) design paradigm. DownloadStruts from apache.org.

Arquillian 1.0.3.FINAL

Arquillian is a testing platform that manages the container lifecycle, deployment andframework initialization. For more information see arquillian.org.

Arquillian Drone 1.1.1.Final

Arquillian Drone is an extension for Arquillian that provides a simple way of includingfunctional tests for applications with a web-based user interface. For more information seearquillian.org.

DeltaSpike 0.3- incubat ing

DeltaSpike consist of a number of portable CDI extensions that provide useful features forJava application developers. For more information see apache.org.

Google Web Toolkit 2.5.0

Google Web Toolkit (GWT) allows developers to quickly build and maintain complex, yethighly performant JavaScript front-end applications in the Java programming language.Download Google Web Toolkit from google.com.

jQuery 1.7.1


8

http://struts.apache.org/download

http://www.arquillian.org

http://arquillian.org/modules/drone-extension/

http://incubator.apache.org/deltaspike/

http://code.google.com/webtoolkit/versions.html

jQuery is a fast and concise JavaScript Library that simplifies HTML document traversing,event handling, animating, and Ajax interactions for rapid web development. DownloadjQuery from jquery.com.

jQuery Mobile 1.1.0

jQuery Mobile is an HTML-based user interface with lightweight code and flexible designs.Download jQuery Mobile from jquerymobile.com.

JRuby 1.7.3

JRuby is a high performance, stable, fully threaded Java implementation of the Rubyprogramming language. Download JRuby from jruby.org.

Note

Please note that in the scope of JBoss Web Framework Kit, JRuby has only beentested with the TorqueBox framework. Using JRuby for any other purpose has notbeen tested and is not supported.

Spring

Spring is a layered Java/Java EE application framework, allowing for developingcomponents that can be used on application servers and in standalone environments.Download all Spring components from springsource.com.

The following Spring versions are certified with this release of JBoss Web Framework Kit.

Spring 3.2.1.RELEASE

Spring Security 3.1.3.RELEASE

Spring Web Flow 2.3.1.RELEASE

Spring Web Services 2.1.2.RELEASE









Spring 2.5.6.SEC03





9

http://docs.jquery.com/Downloading_jQuery

http://jquerymobile.com/download/

www.jruby.org/download

http://www.springsource.com/products/springsource-download-center

Spring Roo 1.2.3.RELEASE has also been tested with this release of JBoss Web FrameworkKit. However, it is only functional with Spring 3.2.0.RELEASE. A workaround exists thatenables you to run Spring Roo 1.2.3.RELEASE with the tested Spring 3.2.1.RELEASE. SeeChapter 7, Known Issues for more details.

2.3. Confirmed Frameworks

Confirmed frameworks are third party frameworks where there is no support from the JBoss team, butRed Hat verifies that the framework runs succesfully on JBoss Enterprise Application Patform,Enterprise Web Platform, and Enterprise Web Server. Any exceptions are noted in the known issuessection.

Apache Cordova 2.0.0

Apache Cordova is a platform for building native mobile applications using HTML, CSSand JavaScript. Download Apache Cordova from cordova.apache.org.

Apache St ruts 2.3.8

Apache Struts provide an open source framework useful in building web applications withJava Servlet and JavaServer Pages (JSP) technology. This framework encouragesapplication architectures based on the Model-View-Controller (MVC) design paradigm.Download Struts from apache.org.

Backbone 0.9 .2

Backbone gives structure to web applications by providing models with key-value bindingsand custom events, collections with a rich API of enumerable functions, views withdeclarative event handling, and the possibility of connection to existing API over a RESTfulJSON interface. Download Backbone from backbonejs.org.

Bootst rap 2.0.2

Bootstrap is a collection of tools for creating websites and web applications. It containsHTML and CSS based design templates for typography, forms, buttons, charts, navigationand other interface components, as well as optional JavaScript extensions. Downloadbootstrap from twitter.github.com.

Flex 4 .6

Flex is a productive, open source framework for building and maintaining expressive webapplications that deploy consistently on all major browsers, desktops and operatingsystems. Download Flex from opensource.adobe.com.

Grails 1.3.9 and 2.2.0

Grails is build on Spring, and based on Groovy. It provides developer productivity byapplying principles like Convention over Configuration. Download Grails from grails.org.

IceFaces 1.8.2 and 3.2.0

IceFaces provides a complete set of enhanced standard and custom JavaServer Faces(JSF) components. Download IceFaces from icefaces.org.

Moderniz r 2.0.6

Modernizr is a JavaScript library that detects the availability of native implementations forfeatures that stem from the HTML5 and CSS3 specifications. Download Modernizr frommodernizr.com


10

http://cordova.apache.org/#download

http://struts.apache.org/download

backbonejs.org

http://twitter.github.com/bootstrap/

http://opensource.adobe.com/wiki/display/flexsdk/Flex+SDK

http://grails.org/Download

http://www.icefaces.org/main/downloads/os-downloads.iface

http://modernizr.com/download/

PrimeFaces 3.5

PrimeFaces is a lightweight open source component suite for Java Server Faces.Download PrimeFaces from primefaces.org.

Play! 2.1.0

Play! makes programming easier with features that increase productivity within the Javaenvironment such as hot-reload, simple stateless MVC architecture, HTTP-to-codemapping, and Groovy expression language. Download Play! from playframework.org.

RequireJS 1.0.8

RequireJS is a JavaScript file and module loader. It is optimized for in-browser use, but itcan be used in other JavaScript environments, like Rhino and Node. Download RequireJSfrom requirejs.org.

Underscore 1.3.2

Underscore is a utility-belt library for JavaScript that provides a lot of the functionalprogramming support that you would expect in Prototype.js (or Ruby), but withoutextending any of the built-in JavaScript objects. Download Underscore fromunderscorejs.org.

2.4 . JBoss Enterprise Web Server Compat ibilit y

This section describes JBoss Web Framework Kit compatibility with the JBoss Enterprise Web Server2.

Compatible JBoss Web Framework Kit components:

Struts

Spring

Spring Security

Spring Web Flow

Spring Web Services

Spring Roo

Arquillian

Arquillian Drone

GWT

JQuery

JQuery Mobile

Apache Cordova

IceFaces (JavaServer Faces 1 only)

PrimeFaces (JavaServer Faces 1 only)

Struts 2


11

http://www.primefaces.org/downloads.html

http://www.playframework.org/download

http://requirejs.org/docs/download.html

http://underscorejs.org/

Play

Flex

Grails

Backbone

RequireJS

Underscore

Bootstrap

Modernizr

Incompatible JBoss Web Framework Kit components:

RichFaces

Seam

Hibernate Search

Errai

TorqueBox

JRuby

JBoss Developer Framework (does not deliver anything related to the JBoss Enterprise WebServer)


12

Chapter 3. Technology Previews

This section describes the Technology Preview features released alongside JBoss Web FrameworkKit.

Technology Preview

Technology Preview features are not fully supported under Red Hat subscription levelagreements (SLAs), may not be functionally complete, and are not intended for productionuse. However, these features provide early access to upcoming product innovations, enablingcustomers to test functionality and provide feedback during the development process. As RedHat considers making future iterations of Technology Preview features generally available, wewill provide commercially reasonable efforts to resolve any reported issues that customersexperience when using these features.

TorqueBox

TorqueBox brings the productivity of Ruby and the Rails Framework to the power of JBoss EnterpriseApplication Platform. TorqueBox supplies not only the fastest Ruby on Rails runtime but also:

clustering

load balancing

asynchronous tasks

scheduled jobs

background services

messaging

supporting queues and topics from JBoss Enterprise Application Platform's internal messagingprovider

CDI

inject Java components into Ruby code.

Errai 2

Errai 2 extends Java EE 6 to the browser. Google Web Toolkit targets developers who are productivewith Java, and want to develop AJAX-like applications with rich behaviour on the client side. TheGoogle Web Toolkit Java-to-JavaScript compiler allows the Java developer to work with their chosennormal editor, and includes debugging and refactoring tools, to manage the large codebases thatcome with rich client development. Errai makes large maintainable rich clients a reality by extendingGoogle Web Toolkit with:

the power of CDI

@Inject into browser/client code

a simple and flexible object-marshalling facility

Chapt er 3. T echnology Previews

13

over-the-wire CDI eventing for a loosely-coupled client-server application with a high performancebi-drectional push, and;

shared code between client and server.

DeltaSpike 0.3-incubat ing

DeltaSpike consist of a number of portable CDI extensions that provide useful features for Javaapplication developers. For more information see apache.org.


14

http://incubator.apache.org/deltaspike/

Chapter 4. Installation Notes

This section contains information related to installing JBoss Web Framework Kit 2.2.0, includinghardware and platform requirements and prerequisites.

Hardware and Software Requirements

JBoss Web Framework Kit requires a working, supported installation of the Java VirtualMachine. Refer tohttp://www.jboss.com/products/platforms/application/supportedconfigurations/ for detailson the supported Java installation for your operating system.JBoss recommends Maven 3 as a minimum requirement for running the included examples.The latest release is the preferred version. You can download Maven from apache.org.

4.1. ZIP Packages Downloadable from Red Hat Customer Portal

This release of JBoss Web Framework Kit is distributed as a series of Z IP files. You can choosewhich Z IP files you want, based on your frameworks and functionality requirements.

jboss-wfk-2.2.0-errai-tech-preview-bin.zip

jboss-wfk-2.2.0-errai-tech-preview-demo.zip

jboss-wfk-2.2.0-errai-tech-preview-src.zip

jboss-wfk-2.2.0-hibernate-search-bin.zip

jboss-wfk-2.2.0-hibernate-search-src.zip

jboss-wfk-2.2.0-maven-repository-compilation.zip

jboss-wfk-2.2.0-maven-repository.zip

jboss-wfk-2.2.0-richfaces-bin.zip

jboss-wfk-2.2.0-richfaces-demo.zip

jboss-wfk-2.2.0-richfaces-src.zip

jboss-wfk-2.2.0-seam23-bin.zip

jboss-wfk-2.2.0-seam23-demo.zip

jboss-wfk-2.2.0-seam23-src.zip

jboss-wfk-2.2.0-snowdrop-bin.zip

jboss-wfk-2.2.0-snowdrop-demo.zip

jboss-wfk-2.2.0-snowdrop-src.zip

jboss-wfk-2.2.0-spring-demo.zip

jboss-wfk-2.2.0-ticketmonster-demo.zip

Chapt er 4 . Inst allat ion Not es

15


http://maven.apache.org/download.html

jboss-wfk-2.2.0-torquebox-tech-preview-bin.zip

jboss-wfk-2.2.0-torquebox-tech-preview-src.zip

jboss-wfk-quickstarts-2.2.0-dist.zip

See Snowdrop User Guide for instructions on installing and using Snowdrop.

Note

The delivery method of the quickstarts and the TicketMonster demo is planned to be changedin the next release of JBoss Web Framework Kit. They will no longer be distributed in the jboss-wfk-quickstarts-2.2.0-dist.zip and jboss-wfk-2.2.0-ticketmonster-demo.zip files and downloadable from Red Hat Customer Portal. Instead,they will be delivered online via jboss.org.

4.2. JBoss Web Framework Kit Maven Repository Installat ion

This release of JBoss Web Framework Kit and the respective release of JBoss Enterpise ApplicationPlatform come with dedicated Maven repositories. These repositories include extra JARs and toolsneeded to run the examples included with the releases. See Maven Repository User Guide forinstructions on installing and configuring these repositories.


16

https://access.redhat.com/home

http://www.jboss.org

Chapter 5. Enhancements

The following enhancement has been made in JBoss Web Framework Kit 2.2.0.

Seam

BZ#874487 - Seam examples should also provide Ant build opt ion

Seam examples could be built using Maven only. Seam's booking example and seamspaceexample can now be built using Maven as well as Ant. However, you must use Ant version1.8.1 or higher to successfully build the examples.

Chapt er 5. Enhancement s

17

https://bugzilla.redhat.com/show_bug.cgi?id=874487

Chapter 6. Fixed Issues

The following is a list of issues fixed in JBoss Web Framework Kit 2.2.0:

Errai

BZ#832066 - Helloworld Errai: javascript validat ion error in JBDS

Invalid JavaScript files were generated by Google Web Toolkit when packaging the helloworld-errai quickstart application using Maven. After importing the packagedapplication into JBoss Developer Studio, errors related to the invalid JavaScript files weredisplayed. The issue has been fixed and the application can be packaged and importedwithout errors.

BZ#873365 - Errai quickstart archetype: Following guide Chapter 2. Errai CDI MavenArchetype: "mvn site" will cause maven hanging (no jacoco report )

The Errai Quickstart Guide contained various incorrect example commands. Theseincluded the commands that generate Errai projects from Maven archetypes, and thesubsequent commands used to work with the generated projects. The example commandshave been fixed throughout the guide and their execution now produces expected results.

BZ#873593 - Ehancement : Errai quickstart : Following guide Chapter 3. Errai JAX-RSMaven Archetype: "mvn test -Pintegrat ion- test" produces error output

The AbstractErraiJaxrsTest test case, which is included in the jaxrs-quickstartMaven archetype, contained multiple subsequent IoC bootstrap calls. Consequently,execution of the test produced errors, even though the test itself passed. The test case hasbeen modified so that only a single bootstrap call is performed. This fixed the issue and theerrors are no longer produced by the test.

BZ#877080 - Vio lat ion of JSR-29 9 in errai bus serializ at ion demo

Managed beans with public fields must be declared with the @Dependent scope to meet§3.1 of the JSR-299 specification. Importing the bus-examples into JBoss DeveloperStudio failed with an error, because the Serialization bean included in the Errai bus-examples was not declared with the scope and contained the public clientEndpointfield,. The clientEndpoint field has been changed from public to protected. Thiseliminates the error and the examples can be imported successfully.

BZ#877117 - errai cd i stock demo - bad url o f the applicat ion

The errai-cdi-stock-demo quickstart application contained the jboss-web.xml file,which was left over from a different quickstart application and should not have beenincluded. Consequently, an incorrect URL was accessed when the applicaton wasdeployed to a web server and displayed using the built-in browser in JBoss DeveloperStudio. The leftover jboss-web.xml file has been removed, ensuring the application isnow accessed at the correct URL and displayed successfully.

Hibernate Search

BZ#878020 - Hibernate Search assembly fails on missing f iles (copyright .txt andlgpl.txt )

The Hibernate Search assembly descriptor referenced files that did not exist in thedistribution. As a consequence, Hibernate Search could not be built from source. This issuehas been fixed by including the referenced files in the distribution. As a result, HibernateSearch can now be built from source successfully.


18







BZ#855948 - Fields declared on @MappedSuperclass parent are not recogniz ed onchild ent ity by programmat ic API mapping

Programmatic API mapping does not recognize Hibernate Search fields inherited fromparent entities annotated with @MappedSuperclass. As a consequence, Hibernate Searchviews the fields as unmapped, resulting in a SearchException. This is not considered abug, but a by-design behaviour that can only be addressed by a functionalityenhancement. Until the functionality is enhanced, the issue can be worked around byoverriding the getter methods of the inherited fields in the child entities.

RichFaces

BZ#801048 - Compilat ion of Input UI component logs 2 errors about faces-conf ig .xml

Compiling RichFaces UI components logs two errors related to the faces-config.xmlfile. As the errors do not affect the functionality of the build, the issue is no longerconsidered a bug and will not be addressed in the future releases.

BZ#822205 - Richfaces kitchensink archetype - creat ing new member f rom iPhonecauses broken push update on mobile devices

When creating a new member in the KitchenSink example application using a web browseron an iOS device, the list of new members failed to get updated correctly. This occurredeven if a new member was subsequently added using a desktop-based web browser. Theunderlying source code has been fixed and the member list is now updated correctly.

Seam

BZ#867815 - Seam2.3 Conversat ion id not restored f rom page context

JSF2 partial state saving prevented Seam from properly initializing page context duringrestore view phase. As a consequence, the conversation ID was not restored during therestore view phase, which caused erroneous behaviour if a conversation-scopedcomponent was accessed during the phase. To fix this issue, Seam has been changed topropagate conversation ID through the query string part of the URL. As a result, properconversation ID is now available during the restore view phase and conversation-scopedcomponents work properly even if accessed during the phase.

BZ#876999 - Seam2.3 remot ing/chat room example doesn' t seem to work with IE 9

The Seam 2.3 chat room example did not work correctly when viewed in Internet Explorer 9.The example displayed JavaScript errors. This issue seems to have been fixed, and theexample works correctly in Internet Explorer 9.

Note

This was a known issue in the previous release and seems to have been resolvednow. However, the fix is not guaranteed.

BZ#877063 - Seam 2.3 seam-gen generated pro ject is not testable

The seam-gen SeamTest template was not properly migrated to Arquillian. As aconsequence, seam-gen tests did not work. To fix this issue, seam-gen SeamTesttemplate has been modified to properly use Arquillian. As a result of the fix, the testsgenerated by seam-gen can now be run with ant test.


19







BZ#877082 - Seam 2.3, JBDS: EL complet ion doesn' t work on Ent ityHome objects

JBoss Developer Studio could not find EntityHome objects for autocompletion. As aconsequence, autocompletion for WebContent did not work. This issue has been fixed inJBoss Developer Studio 6.0.0.GA release and autocompletion now works correctly.

BZ#877374 - Seam2.3 s:cache enabled at t ribute is false by default

The s:cache element had an incorrect default value of false. As a consequence, cachingdid not work by default. This has been fixed and the s:cache element has cachingenabled by default.

BZ#877414 - Seam2.3 s:validateEquality required at t ribute is false by default(should be t rue)

The s:validateEquality element contained the required attribute that had anincorrect default value of false. As a consequence, this contrasted with the documentationand previous behavior. This has been fixed and the default value of the required attributeis set to true.

BZ#877447 - Seam2.3 readme.txt refers to non-exist ing "doc/reference/en-US"directory

The jboss-wfk-2.1.0/jboss-seam-2.3.0.Final-redhat-1/readme.txt filedistributed with JBoss Web Framework Kit contained an invalid link to the communitydocumentation. This issue has been fixed.

BZ#878006 - Seam2.3 b log example usesorg.h ibernate.search.errors.EmptyQueryExcept ion

The Seam blog example is configured to handle the exception org.hibernate.search.errors.EmptyQueryException. This exception was notpresent in Hibernate Search contained in the previous version of JBoss Web Framework Kit.As a consequence, the example did not handle the case where the query contained onlystoplist tokens. This has been fixed by upgrading Hibernate Search to a version whichcontains the org.hibernate.search.errors.EmptyQueryException. As a result, theSeam blog example handles the exception org.hibernate.search.errors.EmptyQueryException correctly.

BZ#876969 - Seam2.3 seam23migrat ion.txt refers to community versions

The distributed seam23migration.txt file contained outdated instructions. To fix thisissue, the seam23migration.txt file has been updated with the correct information.

Security Issues

BZ#512921 - (CVE-2009 -26 25) CVE-2009 -26 25 xerces- j2, JDK: XML parsing Denial-O f -Service (6 84 5701)

Seam and RichFaces used the xerces:xercesImpl:2.9.1-patch01 artifact, which isvulnerable to the CVE-2009-2625 denial-of-service flaw. The artifact has been replacedwith xerces:xercesImpl:2.9.1-redhat-3, which is no longer vulnerable to thedenial-of-service flaw.

Snowdrop

BZ#820740 - Snowdrop sources cannot be built out of the box

Snowdrop sources could not be compiled out of the box because they required artifacts


20








https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-2625


that were not present in Maven Central nor in the Maven repositories distributed with JBossWeb Framework Kit. To fix this issue, the dependencies on missing artifacts have beenupdated to versions that are present in the JBoss Enterprise Application Platform 6.0.1Maven repository, and several unnecessary transitive dependencies have been excluded.As a result of the fix, Snowdrop sources can be compiled out of the box successfully.

Spring

BZ#785684 - Consumers of Spring 3.0 and 3.1 BOMs must include WS Coordinatorwhen running on JBoss Enterprise Web Server

The 3.0, 3.1, and 3.2 versions of the Spring JBoss Stack (BOM file) distributed with JBossWeb Framework Kit were previously compatible only with JBoss Enterprise ApplicationPlatform. To use them with JBoss Enterprise Web Server, an additional dependency had tobe specified. The issue has been fixed and the JBoss Stacks are now compatible withJBoss Enterprise Web Server out of the box.

BZ#796313 - Spring ResourceAdapters are not JCA 1.5 and JCA 1.6 compliant

The SpringContextResourceAdaptor present in Spring versions tested with JBossWeb Framework Kit 2.1.0 violated section 5.3.1 of the JCA 1.5 specification, and did not fullyimplement JCA 1.5 and 1.6. Consequenly, deployment of RAR archives containingpackaged Spring files failed on JBoss Enterprise Application Platform. The issue has beenfixed in Spring 3.1.4.RELEASE and Spring 3.2.1.RELEASE, but Spring 3.0.7.RELEASE andSpring 2.5.6.SEC03 are still affected. Description of a workaround that allows successfuluse of the affected versions has been included in Spring Installation Guide.

TicketMonster

BZ#877086 - T icket Monster: Validat ion errors when import ing to JBDS 5.0.1.GA

JavaScript validity errors were displayed after importing the TicketMonster example intoJBoss Developer Studio. Incorrect validation logic in JBoss Developer Studio caused thiserror, but did not have any effect on the functionality of the example. A snippet that disablesJavaScript validation is now shipped with the example so that the errors are no longerdisplayed.

TorqueBox

BZ#874439 - Error when running eap_overlay script with JRuby 1.7.0.0 on Solaris

Due to an issue in JRuby 1.7.0, execution of the torquebox_eap_overlay.rb scriptfailed on machines running the Solaris operating systems. The issue has been fixed inJRuby 1.7.3, which is the version tested with this release of JBoss Web Framework Kit, andthe script can now be executed successfully on all supported operating systems.

BZ#949947 - Torquebox - ArrayIndexOutOfBoundsExcept ion during startup

When booting a TorqueBox server with multiple deployed applications, one of theapplications sometimes failed to get deployed with a java.lang.ArrayIndexOutOfBoundsException, java.lang.IndexOutOfBoundsException, or an Application root does not exist error message followed by an incorrect path to one of the applications' rootdirectories. This was caused by a thread safety issue in the Ruby ERB library, throughwhich the contents of *-knob.yml deployment descriptors are passed so that


21






environment variables and other expressions can be used inside the descriptors. To fix theissue, TorqueBox was modified to pass in a new binding (execution context) whenever theERB library is used. As a result, TorqueBox servers with multiple deployed applications nolonger have some of those applications randomly fail to deploy.

Quickstarts

BZ#877311 - Errors in 'example-wfk-set t ings.xml' in JBoss WFK Quickstarts

The settings-wfk-example.xml file distributed as a part of the JBoss Web FrameworkKit quickstart applications specified a mirror element that resulted in non-resolvable JBossWeb Framework Kit artifacts. This issue has been fixed by not using the mirror element inthe settings-wfk-example.xml file. As a result, the Boss Web Framework Kit artifactsare resolved appropriately.


22


Chapter 7. Known Issues

The following issues are known to be present in JBoss Web Framework Kit 2.2.0:

Arquillian

BZ#875031 - Deadlock condit ion in TarGZ handling

The ShrinkWrap TarGzExporter implementation contains a race condition which canresult in a deadlock while exporting an archive to a tar.gz file. This bug is still underinvestigation. As a workaround, use the Z IP-based implementation to import or export fileswith ShrinkWrap, instead of the tar.gz implementation. The Z IP-based implementation isknown to work on all platforms.

BZ#881017 - Arquillian AS7 7.1.1.Final adaptor does not work with jmx protocol withEAP 6 .0.1

The OSGi layer, which was present but disabled in JBoss Enterprise Application Platform6.0.0, has been completely removed in JBoss Enterprise Application Platform 6.0.1.Consequently, the Arquillian AS7 JMX protocol is not functional due to missing classes.

To work around the issue, force Arquilllian to use the Servlet protocol by adding <defaultProtocol type="Servlet 3.0"/> under the <arquillian> element in thearquillian.xml file. Then add the following servlet dependency to your project's pom.xml file:

<dependency> <groupId>org.jboss.arquillian.protocol</groupId> <artifactId>arquillian-protocol-servlet</artifactId> <scope>test</scope></dependency>

Errai

BZ#865415 - Errai: deployment of the erraijpa-demo-basic example logs guavarelated errors

Errai requires version 12.0 or newer of the Google Guava library, but JBoss WebFramework Kit and JBoss Enterprise Application Platform have standardized on version11.0. The pom.xml descriptor for the Errai examples have been modified to use GoogleGuava version 12.0 at compile time, since it is strictly required. In runtime, the examples useversion 11.0.

Due to this behavior, the following error appears in the console log when either of the ErraiJPA examples are deployed:

ERROR [stderr] (MSC service thread 1-4) java.util.concurrent.ExecutionException: java.lang.NoSuchMethodError: com.google.common.util.concurrent.MoreExecutors.sameThreadExecutor()Lcom/google/common/util/concurrent/ListeningExecutorService;

The appearance of this error is expected and can be disregarded.

BZ#883918 - Errai is not compat ib le with GWT 2.5.0


23





Due to changes introduced in Google Web Toolkit 2.5.0, compiling Errai with GWT 2.5.0fails with errors related to the UIBinder class. It is therefore not recommended to use Erraiwith GWT 2.5.0, even if GWT is used only as a runtime. However, please note that GWT2.4.0 exposes a cross-site scripting (XSS) flaw identified by CVE-2012-5920. Noworkaround for this flaw is currently known. The flaw will be addressed in a future release ofErrai.

BZ#921049 - Errai Kitchen Sink Maven Archetype 2.2.1-SNAPSHOT - validat ion errorin GWT development mode

Compiling a project generated from the Errai Kitchen Sink Maven archetype using GWTMaven Plugin fails with all versions of OpenJDK 7 and Oracle JDK 7 update 16 or earlier.To work around the issue, compile the project with any version of Oracle JDK 6 orOpenJDK 6, or Oracle JDK 7 update 17 or later. The compiled project can then be deployedwith any JDK.

General Issues

BZ#870349 - Guava versions in Errai and RichFaces are not compat ib le

RichFaces and Errai are both included components in JBoss Web Framework Kit, and eachuses a different version of Google Guava. As a result, when they are used together in thesame project, the following error may occur:

java.lang.NoClassDefFoundError: com/google/common/reflect/TypeToken

To resolve this issue, force your build to use Google Guava version 12.0. To do this, youcan add the following XML to your Maven pom.xml :

<dependencyManagement> <dependencies> <dependency> <groupId>com.google.guava</groupId> <artifactId>guava</artifactId> <version>12.0</version> </dependency> </dependencies></dependencyManagement>

After you specify the version which should be used, the error no longer occurs.

BZ#919361 - Imported Deltaspike Beanmanager quickstart shows a warning in JBDS6

After importing the deltaspike-beanmanagerprovider quickstart application into JBossDeveloper Studio 6, a JPA module is detected, but is not configured because no JPAconnection is defined. Consequently, the following warning is displayed:

Console configuration "jboss-as-deltaspike-beanmanagerprovider" does not exist. jboss-as-deltaspike-beanmanagerprovider line 0 JPA Problem

As this issue does not influence the functionality of the example, it can be worked aroundby disabling JPA validation. To disable JPA validation, right-click the application in Project


24

https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-5920




Explorer, choose Properties from the context menu, select Validation in the displayedwindow, enable the Enable project specific settings option, and uncheck the two boxes inthe JPA Validator line.

BZ#913165 - Repeat : input inside repeat in not updated

The input HTML element rendered by the h:inputText JSF component does not containthe value attribute. Consequently, when entering text in the input field, submitting it andtrying to clear the input text by clearing the bound value on the server side, the receivedpartial update does not clear the input field in the browser.

The issue originates in Mojarra 2.1.13, which is included in JBoss Enterprise ApplicationPlatform 6.0.1. JBoss Enterprise Application Platform 6.0.0 is not affected by this issue as itcontains a different version of Mojarra. No workaround for this issues is currently known.

BZ#790873 - Grails applicat ions cannot be deployed to EAP unless OSGi is d isabled

OSGi is not enabled in JBoss Enterprise Application Platform 6. Artifacts produced byGrails miss a Package-Import of javax.naming in the bundle. The workaround for thisissue is to disable OSGi while packaging your Grails applications. You can do this usingthe following configuration in the BuildConfig.groovy configuration file:

grails.project.war.osgi.headers = false

Google Web Toolkit

BZ#803780 - Wrong popup behavior in GWT on iOS devices

iPad and iPhone devices ignore single-tap events outside pop-up elements, whichsubsequently do not disappear when users tap outside the element area. With the Imageelement, you can work around the issue with a single tap directly on the image. With the Date Picker element, picking a date makes it disappear. With the Simple Text Area,you can work around the issue by activating a different element on the page. With all otherelements, the workaround is to navigate to a different page and then back.

BZ#803782 - GWT: Unable to edit text inside of RichTextArea element on mobiledevices

Some iOS and Android devices treat RichTextArea as a read-only HTML element.Consequently, the devices fail to activate the RichTextArea and write text into it. Theworkaround is to avoid using RichTextArea elements in applications accessed by mobiledevices. Other HTML elements are not affected by this issue.

BZ#919447 - GWT fails on IBM Java 1.6 and 1.7

Google Web Toolkit attempts to load pre-compiled GWT module archives (.gwtar files) toincrease performance. Consequently, building GWT examples shipped with this releasefails with the IBM implementations of the Java Developement Kit (both 1.6 and 1.7). To workaround the issue, use the -Dgwt.usearchives=false parameter with gwt-maven-plugin to disable loading of the pre-compiled archives.

RichFaces

BZ#802444 - RichFaces Showcase - JMS Push: HornetQ JMS connect ion is securedby default

The default installation of JBoss Enterprise Application Platform and JMS Push, which isrequired by the RichFaces Showcase example, are secured. To deploy the application, you


25







need to add a new user to the ApplicationRealm using the $JBOSS_HOME/bin/add-user.bat or add-user.sh script, with the guest role. Then modify the web.xml file in theRichFaces Showcase and replace ${username} and ${password} with the actualcredentials. The XML containing the two replaceable values is shown below.

<context-param> <param-name>org.richfaces.push.jms.connectionUsername</param-name> <param-value>${username}</param-value></context-param><context-param> <param-name>org.richfaces.push.jms.connectionPassword</param-name> <param-value>${password}</param-value></context-param>

After adding the user to the ApplicationRealm and adding the credentials to theapplications's web.xml , the application will work correctly.

BZ#822210 - Richfaces kitchensink archetype - it should be possib le to return f romviewing details about member back to the list o f all members on mobile devices

The browser interface of the KitchenSink example application does not include a link ornavigation button to allow you to return from the Details view to the List view on mobiledevices. To work around this limitation, use the Home button, then click the List of People link.

BZ#952235 - a4 j:push component RichFaces backward compat ib ility problem

Applications created with RichFaces 4.2.3.Final, which is the version shipped with JBossWeb Framework Kit 2.1.0, contain a dependency on the 0.8.4 version of the Atmosphereframework, which is not backward compatible with RichFaces 4.3.1.Final shipped with thisrelease. Consequently, the a4j:push component does not provide any push updateswhen the application is used with RichFaces 4.3.1.Final. To work around the issue, changethe Atmosphere depencency to version 1.0.10 , or replace the Atmosphere libraries withthe respective versions. As a result of the workaround, the a4j:push component providespush updates correctly.

Seam

BZ#867381 - Seam2.3 seam-gen generated act ion shows "The form componentneeds to have a UIForm in its ancest ry. . . ." message

On submitting a JSF request, a JSF warning message is displayed. As a workaround forthis issue, use the PRODUCTION value for javax.faces.PROJECT_STAGE in web.xmlas follows:

<context-param> <param-name>javax.faces.PROJECT_STAGE</param-name> <param-value>Production</param-value></context-param>

As a result, the JSF request is submitted successfully.


26




BZ#875614 - Seam2.3 sporadic NPE inorg.jboss.seam.jms.TopicSession.create(TopicSession.java:38)

By design, Seam puts newly instantiated components into the scopes before calling the @Create or @PostConstruct methods. The TopicConnection and QueueConnection Seam JMS components do not synchronize access to their @Createand @Unwrap methods. This causes multiple concurrent requests that are the first to requirethese components to inject instances of these built-in application-scoped componentsbefore they are instantiated.

To work around this issue, you can force the components to be created during applicationstart-up. In this case, there is no risk of this race condition occurring. The followingexample code shows how to apply this work-around:

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

If you apply the work-around, the components are created during application start-up andno race condition occurs.

BZ#875656 - XML validat ion errors af ter import ing Blog example to JBDS

After importing the Maven Blog example into JBoss Developer Studio, the following threeerrors are displayed:

cvc-elt.1: Cannot find the declaration of element 'f:view'.

Referenced file contains errors (file:/jbdevstudio-6.0.0.Beta1/studio/plugins/org.jboss.tools.jst.web.kb_3.4.0.Beta1-v20121018-0628-B39/taglibs/tld/facelets_jsf_core.taglib.xml).

Referenced file contains errors (file:/jbdevstudio-6.0.0.Beta1/studio/plugins/org.jboss.tools.jst.web.kb_3.4.0.Beta1-v20121018-0628-B39/taglibs/tld/html_basic.taglib.xml).

Currently, there is no workaround for this issue.

BZ#878496 - For Seam 2.3 seam-gen generated pro ject , JBDS reports missing f ilesreferenced f rom viewid in pages.xml

When a seam-gen generated project is imported into JBoss Developer Studio, the projectconfiguration is insufficient to correctly supply and validate the Seam pages.xml file. As aconsequence, JBDS displays the following warning message:

Cannot find target resource: "/home.xhtml".

As a workaround for this issue, change the project type to a Facet Project. In Project properties, go to Project Facets and choose Seam, Dynamic Web project, andthe Java Server Faces options.


27




BZ#878505 - In Seam 2.3 seam-gen generated pro ject imported in JBDS, ELcomplet ion for Seam Messages doesn' t work

When a seam-gen generated project is imported into JBoss Developer Studio, the projectconfiguration is insufficient to correctly supply and validate Seam Messages propertiesused in pages.xml or messages.properties. As a consequence, JBoss DeveloperStudio displays the following warning message:

#{messages['org.jboss.seam.NotLoggedIn']} cannot be resolved

As a workaround for this issue, change the project type to a Facet Project. In Project properties, go to Project Facets and choose Seam, Dynamic Web project, andthe Java Server Faces options.

BZ#912394 - Seam2.3 Components included with u i:include src= "#{pageScopedViewId} broken

Inserting a page-scoped UI view component into facelet fragment does not work due to JSFdesign issue in partial restore processing. As a consequence, you cannot use page scopeUI view components with the <ui:include> tag. As a workaround for this issue, disable PARTIAL_STATE_SAVING by inserting the following configuration in the web.xml file:

<context-param> <param-name>javax.faces.PARTIAL_STATE_SAVING</param-name> <param-value>false</param-value></context-param>

Alternatively, you can use selective full state saving mode only for viewId , which requires PageScope viewID components, and partial state saving mode does not work for it.

<context-param> <param-name>javax.faces.FULL_STATE_SAVING_VIEW_IDS</param-name> <param-value>/index.xhtml,/component1.xhtml,/component2.xhtml</param-value></context-param>

As a result of the workaround, you can use a page-scoped UI view component.

BZ#916998 - Seam2.3 seam-gen ivy broken

Seam-gen generated project cannot use maven dependency management through ivy. As aresult, you cannot use the seam-gen command seam add-ivy. Currently, there is noworkaround for this issue.

BZ#922049 - seam2.3 seam-gen resources- test /arquillian .xml not used

In Seam 2.3, the resources-test/arquillian.xml configuration file is not used whenrunning ant test. To use the Arquillian configuration specified in the file, move theconfiguration file to the root of your generated project.

BZ#922059 - seamspace example occasionally fails with a npe on ibm jvm


28






On IBM virtual machines, the seamspace example fails with a NullPointerExceptionwhile submitting a new blog entry. This issue is caused by an issue in the IBM virtualmachines. The fix for this issue has been deferred until a fix to the IBM virtual machines isintroduced.

BZ#876999 - Seam2.3 remot ing/chat room example doesn' t seem to work with IE 9

The Seam 2.3 chat room example does not work correctly when executed in InternetExplorer 9. Instead, the example displays JavaScript errors. As a workaround, use adifferent version of Internet Explorer or an alternative Internet browser.

Note

This was a known issue in the previous release and seems to have been resolvednow. However, the fix is not guaranteed.

BZ#869638 - Seam2.3: TAG-16 Groovybooking example

The Seam groovybooking example uses the maven-antrun-plugin, which cannot beimported into JBoss Developer Studio automatically. As a consequence, the examplecannot be built automatically in JBoss Developer Studio. As a workaround, use the mvn clean package Maven command to build the example.

BZ#902905 - Seam2.3 @DataModel & @DataModelSelect ion doesn' t work withrichfaces4 dataTable

The UIDataTable component (the <rich:dataTable> element) shipped with RichFaces4 does not extend the JSF UIData class. As a consequence, rendering of Seamcomponents annotated with @DataModel and @DataModelSelection inside a UIDataTable does not work as expected. To work around the issue, use the JSF DataTable (the <h:dataTable> element) instead of the Richfaces UIDataTable.

BZ#950929 - Seam2.3 seam-gen generated pro jects are missing some lib /testslibraries

The .classpath files of projects generated by seam-gen do not get updated after thefollowing JAR archives are removed:

lib/test/jboss-remoting-3.2.13.GA-redhat-1.jar

lib/test/xnio-api-3.0.3.GA.jar

lib/test/xnio-nio-3.0.3.GA.jar

Errors about missing library JARs are consequently displayed in JBoss Developer Studio.To work around the issue, remove the JARs from build classpath manually: go to projectPropert ies → Build Path → Conf igure Build Path → Libraries , select the JARs andclick the Remove button. As a result of the workaround, the errors will no longer bedisplayed.

BZ#951044 - Seam2.3 seam-gen EAR project explode target touches .dodeployforcing a restart , prevent ing hot -deployment

The Ant build.xml file of an EAR application generated by seam-gen contains an errorthat influences the logic used to determine if the deployed application should be restartedafter being updated. As a consequence, the application is always restarted, even in caseswhere hot deployment would normally be performed. To work around the issue, replace the


29






following part of the build.xml file:

<available file="${deploy.dir}/${project.name}.war.deployed" property="deployed.file.exists"/>

with the following code:

<available file="${deploy.dir}/${project.name}.ear.deployed" property="deployed.file.exists"/>

As a result of the workaround, the deployed EAR application will only be restarted inrelevant cases, and hot deployment will be performed otherwise.

BZ#951540 - Seam2.3 BOM should not declare jboss-as-arquillian-container-{managed|remote} version

Duplicated jboss-as-arquillian-container-managed and jboss-as-arquillian-container-managed-remote artifacts are defined in the dependencyManagement section of the Seam JBoss Stack, causing incorrect versions tobe used. To work around the issue, specify the org.jboss.bom:jboss-javaee-6.0-with-tools:1.0.4.Final-redhat-wfk-1 JBoss Stack before importing the SeamJBoss Stack. As a result of the workaround, dependencyManagement entries from the jboss-javaee-6.0-with-tools JBoss Stack will be detected by Maven first, and theduplicated artifacts and their versions will not be taken into account.

BZ#903177 - Seam2.3 localiz at ion set t ings via component .xml doesn' t work

When locale-config configuration is used in a Seam application, the following errormessage 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 theapplication. The issue can be worked around by using the 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.

BZ#928002 - Seam2.3 pages rewrite doesn' t rewrite s:link params

Using the <rewrite> configuration in the Seam components.xml file does not ensurecorrect URL rewriting. Because URL rewriting is performed before parameters are set, URLsproduced by the <s:link> and <s:button> elements are rendered with query stringparameters. No workaround for this issue is currently known.

BZ#921660 - Seam2.3 SeamViewHandler adds conversat ion id even if conversat ion isnot long running

Seam redirect URLs always contain the cid querystring parameter specifying aconversation ID, even in cases where long running conversations do not take place. Noworkaround for this issue is currently known.


30





BZ#921878 - Seam2.3 seam-gen NCDFE org.slf4 j.impl.Stat icLoggerBinder on IBMJVM

Running seam generate on IBM Java Virtual Machines fails with the following error:

java.lang.NoClassDefFoundError:org.slf4j.impl.StaticLoggerBinder

Consequently, it is not possible to perform reverse engineering of database entities using seam-gen on IBM Java Virtual Machines. No workaround for this issue is currently known.

BZ#948265 - Seam2.3 SeamInterceptor doesn' t work on EJB @Schedule methods

Seam does not implement support for EJB 3.1 timers. As a consequence, features like Seambijection do not work with EJB 3.1 timers. To work around this issue, timeout methods canuse Lifecycle.beginCall() and Lifecycle.endCall() methods for each timeoutinvocation, and use the Component.getInstance() method to get instances ofapplication-scoped components.

BZ#948215 - Seam2.3 javax.naming.NameNotFoundExcept ion t rying to call EJB Seamcomponents f rom quartz asynchronous methods

Calling EJB Seam components from non-EJB threads (for example asynchronous Quartzthreads) does not work due to a different implementation of the JNDI pattern specification inJava EE 6. As a consequence, the javax.naming.NameNotFoundException exceptionis generated while looking for EJB components from a non-EJB thread. The workaround forthis issue is actually the correct method of accessing EJB components: accessing EJBcomponents from non-EJB threads by global JNDI and not by application JNDI.

BZ#952571 - Seam produces malformed part ial response on ViewExpiredExcept ionwith Ajax

The partial-response elements in AJAX responses produced by Seam are duplicated.Consequently, redirection rules defined in the pages.xml file are not correctly processedand therefore not followed. No workaround for this issue is currently known.

Security Issues

BZ#873317 - (CVE-2012-5783) CVE-2012-5783 jakarta-commons-ht tpclient : missingconnect ion hostname check against X.509 cert if icate name

Apache Commons HttpClient 3 is vulnerable to CVE-2012-5783, a security flaw related toincorrect validation of X.509 certificates. HttpClient 3 has reached its end of life as acomponent maintained by Apache, and no upstream build is available that addresses thisflaw. The version of HttpClient 3 that is shipped with JBoss Web Framework Kit 2.2.0 hasbeen built by Red Hat and includes a patch for this flaw. HttpClient 3 versions consumedfrom Maven Central do not have this patch applied. Apache Commons HttpClient 3 is atransitive dependency of multiple components included in JBoss Web Framework Kit 2.2.0.If this dependency is resolved using a build of HttpClient 3 obtained from Maven Central,the flaw may be exposed.

Snowdrop

BZ#948702 - Sportsclub: Invoice generat ion fails for account with b ill ing typeSEMIMONTHLY

The SEMIMONTHLY billing type is not implemented in the org.jboss.snowdrop.samples.sportsclub.domain.entity.Account class of


31






https://access.redhat.com/security/cve/CVE-2012-5783


the Sportsclub example. Consequently, generating an invoice for a subscription that hasthe SEMIMONTHLY billing type set fails with an IllegalArgumentException. Noworkaround for this issue is currently known except for extending the implementation byyour own means.

Spring

BZ#760115 - RichFaces with Spring WebFlow requires addit ional conf igurat ion

If you need to use Spring WebFlow 2.3 and RichFaces 4 together, you need to create anextra bean to resolve RichFace resources. This bean is not automatically included as partof faces:resources. If it is not present, a 404 error occurs when a CSS file is requested.

To work around this issue, change the order of the flowMapping so that RichFaces hashigher priority than the user-generated flow (lower numbers get higher priority), and add thefollowing 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, requests for CSS files succeed and no error occurs.

BZ#903235 - Spring SAAJ support together with Sun/Oracle SAAJ implementat iondoesn' t work on IBM JVMs out of the box

The Oracle SAAJ implementation uses internal JDK classes that are not provided with IBMJDKs. This causes compilation errors in applications using Spring SAAJ support togetherwith the Oracle SAAJ implementation and an IBM JDK.

The recommended workaround is to remove Oracle SAAJ JARs from the class path of yourapplication so that the bundled IBM implementation is used instead. The following is anexample of the SAAJ JAR dependency that needs to be removed:

<dependency> <groupId>com.sun.xml.messaging.saaj</groupId> <artifactId>saaj-impl</artifactId> <version>1.3.10</version></dependency>

A second workaround, which may not be functional on IBM JVM 7, is to add the OracleJAXP implementation to the class path:


32



<dependency> <groupId>com.sun.xml.parsers</groupId> <artifactId>jaxp-ri</artifactId> <version>1.4.5</version></dependency>

BZ#916903 - Spring Roo 1.2.3.RELEASE does not work with Spring 3.2.1.RELEASEout of the box due to missing spring-web dependency

Spring Roo 1.2.3 uses Spring Core 3.2.0, whose package structure is different from SpringCore 3.2.1. As a consequence, configuring an application generated by Spring Roo to usethe Spring JBoss Stack distributed with JBoss Web Framework Kit causes compilationerrors. To work around this issue and compile the application successfully, add thefollowing dependency to your project:

<dependency> <groupId>org.springframework</groupId> <artifactId>spring-web</artifactId> <version>3.2.1.RELEASE</version></dependency>

BZ#923377 - Spring 's get t ing-started example shows warnings af ter import ing in toJBDS 6

When the Spring getting-started example is imported into JBoss Developer Studio, variouswarnings are reported. To remove the warnings, add the missing </table> tag before the </form> tag in the src/main/webapp/WEB-INF/views/greet.jsp file. Otherwarnings can be removed by editing the src/main/webapp/index.jsp file and adding <head><meta HTTP-EQUIV="REFRESH" content="0; url=app/greet"></head>right after the <html> tag, and also removing the <h2> element with all its content.

BZ#801406 - Invalid persistent .xml descriptor in the Petclin ic example

When importing the Petclinic example application into JBoss Developer Studio 6, a persistence.xml file with invalid contents is created in the src/main/resources/META-INF/ directory. During deployment, this file has higherpriority than the correct src/main/environments/eap/resources/META-INF/persistence.xml file, and the deployment fails. To work around the issue, removethe invalid src/main/resources/META-INF/persistence.xml file before deployingthe application.

Struts

BZ#803749 - St ruts 1 Showcase applicat ion 's JSF integrat ion does not work onEAP6

The JSF integration in the Struts 1 Showcase application is not functional with JBossEnterprise Application Platform 6. To work around this issue, override the default JSFimplementation by adding the following configuration into the web.xml file of theapplication:

<context-param> <param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-


33





name> <param-value>true</param-value></context-param>

BZ#803747 - St ruts 2 Showcase applicat ion 's JSF integrat ion does not work onEAP6

The JSF integration in the Struts 2 Showcase application is not functional with JBossEnterprise Application Platform 6. To work around this issue, override the default JSFimplementation by adding the following configuration into the web.xml file of theapplication:

<context-param> <param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name> <param-value>true</param-value></context-param>

BZ#803860 - St ruts 2 applicat ion without st ruts.xml fails to deploy on EAP6

A Struts 2 application without the struts.xml descriptor can be deployed on JBossEnterprise Application Platform 6, but actions are not properly mapped. There is no knownworkaround for this issue other then including the struts.xml file in your application.

TicketMonster

BZ#879576 - T icket -monster demo does not work in IE10 properly

JavaScript libraries used in the TicketMonster example are not compatible with InternetExplorer 10. Consequently, some pages of the example website are not rendered at all whenaccessed using Internet Explorer 10. To work around this issue, enable the browser'scompatibility mode or use an alternative browser.

BZ#871099 - T icket Monster: generated Administ rat io in sect ion does not workproperly

Multiple issues occur in the Administration section of the TicketMonster example whenit is generated using JBoss Forge. The root cause of the issue is in the implementation ofJBoss Forge and not in the TicketMonster example. No workaround for this issue iscurrently known.

BZ#950334 - T icket Monster: richfaces-bom version does not align with WFK

RichFaces Plugin for JBoss Forge does not use the RichFaces version distributed withJBoss Web Framework Kit 2.2.0. Consequently, the Administration section of theTicketMonster example uses RichFaces 4.2.2. To work around the issue, perform thefollowing changes in the project's pom.xml file:

Override the dependency version by including the following snippet:

<dependencyManagement> <dependencies> <dependency> <groupId>org.jboss.bom</groupId> <artifactId>jboss-javaee-6.0-with-richfaces</artifactId>


34






<type>pom</type> <scope>import</scope> <version>1.0.4.Final-redhat-wfk-1</version> </dependency> </dependencies></dependencyManagement>

Remove the following snippet:

<dependencyManagement> <dependencies> <dependency> <groupId>org.richfaces</groupId> <artifactId>richfaces-bom</artifactId> <version>4.2.2.Final</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies></dependencyManagement>

Remove the hard-coded versions specified with RichFaces artifacst:

<dependency> <groupId>org.richfaces.ui</groupId> <artifactId>richfaces-components-ui</artifactId> <version>4.2.2.Final</version></dependency><dependency> <groupId>org.richfaces.core</groupId> <artifactId>richfaces-core-impl</artifactId> <version>4.2.2.Final</version></dependency>

As a result of the workaround, the implementation of the Administration section will use thecorrect version of RichFaces.

BZ#929102 - T icket Monster: richfaces-bom can ' t be found during Administ rat ionsect ion generat ion

A bug in JBoss Forge causes the following error when downloading the RichFaces JBossStack with the JBoss Web Framework Kit Maven repository enabled in the activeProfiles section of the settings.xml file:

[ERROR] Non-resolvable import POM: Could not find artifact org.richfaces:richfaces-bom:pom:4.2.2.Final

To work around the issue, fetch the artifact locally by running the mvn verify goal fromthe JBoss Forge console.

BZ#953566 - Some of performance dates have passed so the performances are notshown in `Monitor` sect ion

The sample performances in the TicketMonster example have their dates set to April and


35



May 2013. Consequently, no performances will be displayed in the Monitoring section ofthe example after these dates. To work around the issue, change the dates manually viah2console, in the Administ rat ion section of the example, or directly in the ticket-monster/demo/src/main/resources/import.sql query. As a result, theperformances will be displayed until the newly set dates.

TorqueBox

BZ#915749 - Document that JRuby 1.6 .8 support is dropped for TorqueBox

Using JRuby 1.6.8 to run the TorqueBox distribution shipped with this release of JBossWeb Framework Kit is no longer tested. JRuby 1.7.3 is the only JRuby version tested withthis release.

BZ#876119 - Bundler uses wrong gem version when Gemf ile specif ies ~ >x.x.x.redhat .1

The Bundler gem used in Gemfile for specifying Torquebox versions has had its behaviormodified, causing the ~> operator to not correctly resolve the .redhat.X gem variant. Towork around this issue, specify the exact TorqueBox productized gem version within theGemfile.


36



Chapter 8. Product Support and License Website Links

Product Page

http://www.redhat.com/products/jbossenterprisemiddleware/web-framework-kit/

Support Processes

http://www.redhat.com/support/process/

Product Support Scope of Coverage

https://access.redhat.com/support/offerings/production/soc.html

Product ion Support Service Level Agreement

https://access.redhat.com/support/offerings/production/sla.html

Developer Support Scope of Coverage

https://access.redhat.com/support/offerings/developer/soc.html

Developer Support Service Level Agreement

https://access.redhat.com/support/offerings/developer/sla.html

Product Update and Support Policy by Product

http://www.redhat.com/security/updates/jboss_notes/

JBoss End User License Agreement

http://www.redhat.com/licenses/jboss_eula.html

Chapt er 8 . Product Support and License Websit e Links

37

http://www.redhat.com/products/jbossenterprisemiddleware/web-framework-kit/

http://www.redhat.com/support/process/

https://access.redhat.com/support/offerings/production/soc.html

https://access.redhat.com/support/offerings/production/sla.html

https://access.redhat.com/support/offerings/developer/soc.html

https://access.redhat.com/support/offerings/developer/sla.html

http://www.redhat.com/security/updates/jboss_notes/

http://www.redhat.com/licenses/jboss_eula.html

Revision History

Revision 1-2 Wed Nov 05 2014 Michelle MurrayWFKDOC-100: Fixed typo

Revision 1-1 Tue Apr 23 2013 Petr PenickaPublished with the release of JBoss Web Framework Kit 2.2.0.


38

Date post:	11-Dec-2016
Category:	Documents
Upload:	lamtu
View:	233 times
Download:	3 times

Red Hat JBoss Web Framework Kit 2.2 2.2.0 Release Notes

Documents