1. No category

Red Hat JBoss Web Framework Kit
2.2
2.2.0 Release Notes
for use with JBoss Web Framework Kit
Edition 2.2.0
Red Hat Documentation Team
Red Hat JBoss Web Framework Kit 2.2 2.2.0 Release Notes
for use with JBoss Web Framework Kit
Edition 2.2.0
Red Hat Do cumentatio n Team
Red Hat Engineering Co ntent Services
Legal Notice
Co pyright © 20 13 Red Hat, Inc.
This do cument is licensed by Red Hat under the Creative Co mmo ns Attributio n-ShareAlike 3.0
Unpo rted License. If yo u distribute this do cument, o r a mo dified versio n o f it, yo u must pro vide
attributio n to Red Hat, Inc. and pro vide a link to the o riginal. If the do cument is mo dified, all Red
Hat trademarks must be remo ved.
Red Hat, as the licenso r o f this do cument, waives the right to enfo rce, and agrees no t to assert,
Sectio n 4 d o f CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shado wman lo go , JBo ss, MetaMatrix, Fedo ra, the Infinity
Lo go , and RHCE are trademarks o f Red Hat, Inc., registered in the United States and o ther
co untries.
Linux ® is the registered trademark o f Linus To rvalds in the United States and o ther co untries.
Java ® is a registered trademark o f Oracle and/o r its affiliates.
XFS ® is a trademark o f Silico n Graphics Internatio nal Co rp. o r its subsidiaries in the United
States and/o r o ther co untries.
MySQL ® is a registered trademark o f MySQL AB in the United States, the Euro pean Unio n and
o ther co untries.
No de.js ® is an o fficial trademark o f Jo yent. Red Hat So ftware Co llectio ns is no t fo rmally
related to o r endo rsed by the o fficial Jo yent No de.js o pen so urce o r co mmercial pro ject.
The OpenStack ® Wo rd Mark and OpenStack Lo go are either registered trademarks/service
marks o r trademarks/service marks o f the OpenStack Fo undatio n, in the United States and o ther
co untries and are used with the OpenStack Fo undatio n's permissio n. We are no t affiliated with,
endo rsed o r spo nso red by the OpenStack Fo undatio n, o r the OpenStack co mmunity.
All o ther trademarks are the pro perty o f their respective o wners.
Abstract
These release no tes co ntain impo rtant info rmatio n related to JBo ss Web Framewo rk Kit 2.2.0 .
Yo u sho uld read these release no tes in their entirety befo re installing the JBo ss Web
Framewo rk Kit 2.2.0 .
T able of Cont ent s
T able of Contents
.Preface
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2. . . . . . . . . .
⁠1. Do c ument Co nventio ns
2
⁠1.1. Typ o g rap hic Co nventio ns
2
⁠1.2. Pull-q uo te Co nventio ns
3
⁠1.3. No tes and Warning s
4
⁠2 . G etting Help and G iving Feed b ac k
4
⁠2 .1. Do Yo u Need Help ?
⁠2 .2. We Need Feed b ac k!
4
5
. .hapt
⁠C
. . . .er
. .1. .. Int
. . .roduct
. . . . . .ion
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6. . . . . . . . . .
⁠1.1. O verview
6
. .hapt
⁠C
. . . .er
. .2. .. Component
..........s
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7. . . . . . . . . .
⁠2 .1. Inc lud ed Co mp o nents
7
⁠2 .2. Tes ted Framewo rks
8
⁠2 .3. Co nfirmed Framewo rks
10
⁠2 .4. JBo s s Enterp ris e Web Server Co mp atib ility
11
. .hapt
⁠C
. . . .er
. .3.
. .T. echnology
. . . . . . . . . . Previews
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. 3. . . . . . . . . .
⁠T o rq ueBo x
13
⁠E rrai 2
⁠D eltaSp ike 0 .3-inc ub ating
13
14
. .hapt
⁠C
. . . .er
. .4. .. Inst
. . . .allat
. . . ion
. . . .Not
. . . es
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. 5. . . . . . . . . .
⁠4 .1. ZIP Pac kag es Do wnlo ad ab le fro m Red Hat Cus to mer Po rtal
⁠4 .2. JBo s s Web Framewo rk Kit Maven Rep o s ito ry Ins tallatio n
15
16
. .hapt
⁠C
. . . .er
. .5.
. .Enhancement
. . . . . . . . . . . . s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. 7. . . . . . . . . .
. .hapt
⁠C
. . . .er
. .6. .. .Fixed
. . . . .Issues
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. 8. . . . . . . . . .
. .hapt
⁠C
. . . .er
. .7. .. .Known
. . . . . . Issues
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2. 3. . . . . . . . . .
. .hapt
⁠C
. . . .er
. .8. .. .Product
. . . . . . . Support
. . . . . . . . and
. . . .License
. . . . . . . Websit
. . . . . . e. .Links
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
...........
. . . . . . . . .Hist
Revision
. . . ory
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
...........
1
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
Preface
1. Document Convent ions
This manual uses several conventions to highlight certain words and phrases and draw attention to
specific pieces of information.
1.1. T ypographic Convent ions
Four typographic conventions are used to call attention to specific words and phrases. These
conventions, and the circumstances they apply to, are as follows.
Mo no -spaced Bo l d
Used to highlight system input, including shell commands, file names and paths. Also used to
highlight keys and key combinations. For example:
To see the contents of the file my_next_bestsel l i ng _no vel in your current
working directory, enter the cat my_next_bestsel l i ng _no vel command at the
shell 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 and
all distinguishable thanks to context.
Key combinations can be distinguished from an individual key by the plus sign that connects each
part of a key combination. For example:
Press Enter to execute the command.
Press C trl +Al t+F2 to switch to a virtual terminal.
The first example highlights a particular key to press. The second example highlights a key
combination: a set of three keys pressed simultaneously.
If source code is discussed, class names, methods, functions, variable names and returned values
mentioned within a paragraph will be presented as above, in mo no -spaced bo l d . For example:
File-related classes include fi l esystem for file systems, fi l e for files, and d i r for
directories. Each class has its own associated set of permissions.
Pro p o rt io n al B o ld
This denotes words or phrases encountered on a system, including application names; dialog-box
text; labeled buttons; check-box and radio-button labels; menu titles and submenu titles. For
example:
Choose Syst em → Pref eren ces → Mo u se from the main menu bar to launch
Mo u se Pref eren ces. In the Butto ns tab, select the Left-hand ed mo use check
box and click C l o se 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 g ed it file, choose Ap p licat io n s →
Accesso ries → C h aract er Map from the main menu bar. Next, choose Search →
Fin d … from the C h aract er 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
2
Preface
C haracter T abl e. D ouble-click this highlighted character to place it in the T ext
to co py field and then click the C o py button. Now switch back to your document
and choose Ed it → Past e from the g ed it menu bar.
The above text includes application names; system-wide menu names and items; application-specific
menu names; and buttons and text found within a GUI interface, all presented in proportional bold
and 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 or
variable text. Italics denotes text you do not input literally or displayed text that changes depending
on circumstance. For example:
To connect to a remote machine using ssh, type ssh username@ domain.name at a
shell prompt. If the remote machine is exampl e. co m and your username on that
machine is john, type ssh jo hn@ exampl e. co m.
The mo unt -o remo unt file-system command remounts the named file system.
For example, to remount the /ho me file system, the command is mo unt -o remo unt
/ho me.
To see the version of a currently installed package, use the rpm -q package
command. It will return a result as follows: package-version-release.
Note the words in bold italics above: username, domain.name, file-system, package, version and
release. Each word is a placeholder, either for text you enter when issuing a command or for text
displayed by the system.
Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and
important term. For example:
Publican is a DocBook publishing system.
1.2. Pull-quot e Convent ions
Terminal output and source code listings are set off visually from the surrounding text.
Output sent to a terminal is set in mo no -spaced ro man and presented thus:
books
books_tests
Desktop
Desktop1
documentation drafts mss
downloads
images notes
photos
scripts
stuff
svgs
svn
Source-code listings are also set in mo no -spaced ro man 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
​
​
​
​
3
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
before, "
​
"so cannot be deassigned\n", __func__);
r = -EINVAL;
goto out;
​
​
​
}
​
kvm_deassign_device(kvm, match);
​
kvm_free_assigned_device(kvm, match);
​o ut:
​
mutex_unlock(& kvm->lock);
return r;
​
​}
1.3. Not es 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 should
have 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 to
the current session, or services that need restarting before an update will apply. Ignoring a
box 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 Hat
Customer 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
Preface
Red Hat also hosts a large number of electronic mailing lists for discussion of Red Hat software and
technology. You can find a list of publicly available mailing lists at
https://www.redhat.com/mailman/listinfo. Click on the name of any mailing list to subscribe to that list
or 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 manual
better, we would love to hear from you! Please submit a report in Bugzilla: http://bugzilla.redhat.com/
against the product JB o ss Web Framewo rk K it .
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 when
describing it. If you have found an error, please include the section number and some of the
surrounding text so we can find it easily.
5
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
Chapter 1. Introduction
These release notes contain important information related to JBoss Web Framework Kit 2.2.0. New
features, 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 for
Java applications. The JBoss Web Framework Kit subscription is already included with JBoss
Enterprise Application Platform.
Certification
Red Hat Quality Engineering uses an extensive set of tests to validate against a specific set of
architectural components in our application stack (operating system, database driver,
database, and JVM). The full list of certified environments is available from
http://www.jboss.com/products/platforms/application/supportedconfigurations/.
This certification applies only to the specific component versions listed under Chapter 2,
Components.
6
⁠Chapt er 2 . Component s
Chapter 2. Components
This chapter details the specific components included in JBoss Web Framework Kit, as well as the
specific 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 compliance
with the certified or compatible configurations for each of those platforms. Ensure that your
products are supported by complying with the specifications listed at
http://www.jboss.com/products/platforms/application/supportedconfigurations/.
Important
Examples included with this release of JBoss Web Framework Kit may contain components
which are not certified or supported. These components were present in the original version
and are preserved for consistent functionality. For an authoritative list of supported and
certified components, please consult Section 2.1, “ Included Components” of these Release
Notes.
2.1. Included Component s
Included components are JBoss-owned frameworks where JBoss controls the upstream project and
can guarantee bug-fixes and patches.
Errai 2.2.0.Fin al
Errai is a framework and tool set that leverages the GWT compiler for the building of web
applications.
H ib ern at e Search 4 .2.0.Fin al
Hibernate Search brings the power of full text search engines to the persistence domain
model by combining Hibernate Core with the capabilities of the Apache Lucene™ search
engine.
R ich Faces 4 .3.1.Fin al
RichFaces is a rich component library for JavaServer Faces (JSF) and an advanced
framework for easily integrating AJAX capabilities into business application development.
Seam 2.3.1.Fin al
Seam is a powerful open source development platform for building rich Internet
applications in Java. Seam integrates technologies such as Asynchronous JavaScript and
XML (AJAX), JavaServer Faces (JSF), Java Persistence API (JPA) and Enterprise Java
Beans (EJB).
7
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
Sn o wd ro p 2.0.5.Fin al
Snowdrop is a utilities package that provides JBoss Enterprise Platform-specific extensions
for the Spring framework.
Sn o wd ro p Sp o rt sclu b Examp le
The Sportsclub application provides a real-world-inspired example of integrating Spring
with the JBoss Enterprise Platforms.
T o rq u eB o x 2.3.0
TorqueBox is built on top of the JBoss Application Server and delivers a platform for Ruby
applications.
T icket Mo n st er Examp le
The TicketMonster example showcases how to create a modern web application configured
for mobile and desktop interactoin.
2.2. T est ed 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 patches
are not provided.
Ap ach e St ru t s 1.3.10
Struts provides an open source framework useful in building web applications with Java
Servlet and JavaServer Pages (JSP) technology. This framework encourages application
architectures based on the Model-View-Controller (MVC) design paradigm. D ownload
Struts from apache.org.
Arq u illian 1.0.3.FIN AL
Arquillian is a testing platform that manages the container lifecycle, deployment and
framework initialization. For more information see arquillian.org.
Arq u illian D ro n e 1.1.1.Fin al
Arquillian D rone is an extension for Arquillian that provides a simple way of including
functional tests for applications with a web-based user interface. For more information see
arquillian.org.
D elt aSp ike 0.3- in cu b at in g
D eltaSpike consist of a number of portable CD I extensions that provide useful features for
Java application developers. For more information see apache.org.
G o o g le Web T o o lkit 2.5.0
Google Web Toolkit (GWT) allows developers to quickly build and maintain complex, yet
highly performant JavaScript front-end applications in the Java programming language.
D ownload Google Web Toolkit from google.com.
jQ u ery 1.7.1
8
⁠Chapt er 2 . Component s
jQuery is a fast and concise JavaScript Library that simplifies HTML document traversing,
event handling, animating, and Ajax interactions for rapid web development. D ownload
jQuery from jquery.com.
jQ u ery Mo b ile 1.1.0
jQuery Mobile is an HTML-based user interface with lightweight code and flexible designs.
D ownload jQuery Mobile from jquerymobile.com.
JR u b y 1.7.3
JRuby is a high performance, stable, fully threaded Java implementation of the Ruby
programming language. D ownload JRuby from jruby.org.
Note
Please note that in the scope of JBoss Web Framework Kit, JRuby has only been
tested with the TorqueBox framework. Using JRuby for any other purpose has not
been tested and is not supported.
Sp rin g
Spring is a layered Java/Java EE application framework, allowing for developing
components that can be used on application servers and in standalone environments.
D ownload 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 3.1.4.RELEASE
Spring Security 3.1.2.RELEASE
Spring Web Flow 2.3.1.RELEASE
Spring Web Services 2.1.2.RELEASE
Spring 3.0.7.RELEASE
Spring Security 3.0.7.RELEASE
Spring Web Flow 2.3.1.RELEASE
Spring Web Services 2.1.2.RELEASE
Spring 2.5.6.SEC03
Spring Security 2.0.7.RELEASE
Spring Web Flow 2.0.9.RELEASE
Spring Web Services 1.5.10.RELEASE
9
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
Spring Roo 1.2.3.RELEASE has also been tested with this release of JBoss Web Framework
Kit. However, it is only functional with Spring 3.2.0.RELEASE. A workaround exists that
enables you to run Spring Roo 1.2.3.RELEASE with the tested Spring 3.2.1.RELEASE. See
Chapter 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, but
Red 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 issues
section.
Ap ach e C o rd o va 2.0.0
Apache Cordova is a platform for building native mobile applications using HTML, CSS
and JavaScript. D ownload Apache Cordova from cordova.apache.org.
Ap ach e St ru t s 2.3.8
Apache Struts provide an open source framework useful in building web applications with
Java Servlet and JavaServer Pages (JSP) technology. This framework encourages
application architectures based on the Model-View-Controller (MVC) design paradigm.
D ownload Struts from apache.org.
B ackb o n e 0.9 .2
Backbone gives structure to web applications by providing models with key-value bindings
and custom events, collections with a rich API of enumerable functions, views with
declarative event handling, and the possibility of connection to existing API over a RESTful
JSON interface. D ownload Backbone from backbonejs.org.
B o o t st rap 2.0.2
Bootstrap is a collection of tools for creating websites and web applications. It contains
HTML and CSS based design templates for typography, forms, buttons, charts, navigation
and other interface components, as well as optional JavaScript extensions. D ownload
bootstrap from twitter.github.com.
Flex 4 .6
Flex is a productive, open source framework for building and maintaining expressive web
applications that deploy consistently on all major browsers, desktops and operating
systems. D ownload Flex from opensource.adobe.com.
G rails 1.3.9 an d 2.2.0
Grails is build on Spring, and based on Groovy. It provides developer productivity by
applying principles like Convention over Configuration. D ownload Grails from grails.org.
IceFaces 1.8.2 an d 3.2.0
IceFaces provides a complete set of enhanced standard and custom JavaServer Faces
(JSF) components. D ownload IceFaces from icefaces.org.
Mo d ern iz r 2.0.6
Modernizr is a JavaScript library that detects the availability of native implementations for
features that stem from the HTML5 and CSS3 specifications. D ownload Modernizr from
modernizr.com
10
⁠Chapt er 2 . Component s
PrimeFaces 3.5
PrimeFaces is a lightweight open source component suite for Java Server Faces.
D ownload PrimeFaces from primefaces.org.
Play! 2.1.0
Play! makes programming easier with features that increase productivity within the Java
environment such as hot-reload, simple stateless MVC architecture, HTTP-to-code
mapping, and Groovy expression language. D ownload Play! from playframework.org.
R eq u ireJS 1.0.8
RequireJS is a JavaScript file and module loader. It is optimized for in-browser use, but it
can be used in other JavaScript environments, like Rhino and Node. D ownload RequireJS
from requirejs.org.
U n d ersco re 1.3.2
Underscore is a utility-belt library for JavaScript that provides a lot of the functional
programming support that you would expect in Prototype.js (or Ruby), but without
extending any of the built-in JavaScript objects. D ownload Underscore from
underscorejs.org.
2.4 . JBoss Ent erprise Web Server Compat ibilit y
This section describes JBoss Web Framework Kit compatibility with the JBoss Enterprise Web Server
2.
Compatible JBoss Web Framework Kit components:
Struts
Spring
Spring Security
Spring Web Flow
Spring Web Services
Spring Roo
Arquillian
Arquillian D rone
GWT
JQuery
JQuery Mobile
Apache Cordova
IceFaces (JavaServer Faces 1 only)
PrimeFaces (JavaServer Faces 1 only)
Struts 2
11
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
Play
Flex
Grails
Backbone
RequireJS
Underscore
Bootstrap
Modernizr
Incompatible JBoss Web Framework Kit components:
RichFaces
Seam
Hibernate Search
Errai
TorqueBox
JRuby
JBoss D eveloper Framework (does not deliver anything related to the JBoss Enterprise Web
Server)
12
⁠Chapt er 3. T echnology Previews
Chapter 3. Technology Previews
This section describes the Technology Preview features released alongside JBoss Web Framework
Kit.
T echnology Preview
Technology Preview features are not fully supported under Red Hat subscription level
agreements (SLAs), may not be functionally complete, and are not intended for production
use. However, these features provide early access to upcoming product innovations, enabling
customers to test functionality and provide feedback during the development process. As Red
Hat considers making future iterations of Technology Preview features generally available, we
will provide commercially reasonable efforts to resolve any reported issues that customers
experience when using these features.
T orqueBox
TorqueBox brings the productivity of Ruby and the Rails Framework to the power of JBoss Enterprise
Application 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 messaging
provider
CD I
inject Java components into Ruby code.
Errai 2
Errai 2 extends Java EE 6 to the browser. Google Web Toolkit targets developers who are productive
with Java, and want to develop AJAX-like applications with rich behaviour on the client side. The
Google Web Toolkit Java-to-JavaScript compiler allows the Java developer to work with their chosen
normal editor, and includes debugging and refactoring tools, to manage the large codebases that
come with rich client development. Errai makes large maintainable rich clients a reality by extending
Google Web Toolkit with:
the power of CD I
@Inject into browser/client code
a simple and flexible object-marshalling facility
13
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
over-the-wire CD I eventing for a loosely-coupled client-server application with a high performance
bi-drectional push, and;
shared code between client and server.
Delt aSpike 0.3-incubat ing
D eltaSpike consist of a number of portable CD I extensions that provide useful features for Java
application developers. For more information see apache.org.
14
⁠Chapt er 4 . Inst allat ion Not es
Chapter 4. Installation Notes
This section contains information related to installing JBoss Web Framework Kit 2.2.0, including
hardware and platform requirements and prerequisites.
Hardware and Software Requirements
JBoss Web Framework Kit requires a working, supported installation of the Java Virtual
Machine. Refer to
http://www.jboss.com/products/platforms/application/supportedconfigurations/ for details
on 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 Cust omer Port al
This release of JBoss Web Framework Kit is distributed as a series of Z IP files. You can choose
which 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
15
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
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 changed
in the next release of JBoss Web Framework Kit. They will no longer be distributed in the
jbo ss-wfk-q ui ckstarts-2. 2. 0 -d i st. zi p and jbo ss-wfk-2. 2. 0 ti cketmo nster-d emo . zi p files and downloadable from Red Hat Customer Portal. Instead,
they will be delivered online via jboss.org.
4 .2. JBoss Web Framework Kit Maven Reposit ory Inst allat ion
This release of JBoss Web Framework Kit and the respective release of JBoss Enterpise Application
Platform come with dedicated Maven repositories. These repositories include extra JARs and tools
needed to run the examples included with the releases. See Maven Repository User Guide for
instructions on installing and configuring these repositories.
16
⁠Chapt er 5. Enhancement s
Chapter 5. Enhancements
The following enhancement has been made in JBoss Web Framework Kit 2.2.0.
Seam
BZ#874487 - Seam examp les sh o u ld also p ro vid e An t b u ild o p t io n
Seam examples could be built using Maven only. Seam's booking example and seamspace
example can now be built using Maven as well as Ant. However, you must use Ant version
1.8.1 or higher to successfully build the examples.
17
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
Chapter 6. Fixed Issues
The following is a list of issues fixed in JBoss Web Framework Kit 2.2.0:
Errai
BZ#832066 - H ello wo rld Errai: javascrip t valid at io n erro r in JB D S
Invalid JavaScript files were generated by Google Web Toolkit when packaging the
hel l o wo rl d -errai quickstart application using Maven. After importing the packaged
application into JBoss D eveloper Studio, errors related to the invalid JavaScript files were
displayed. The issue has been fixed and the application can be packaged and imported
without errors.
BZ#873365 - Errai q u ickst art arch et yp e: Fo llo win g g u id e C h ap t er 2. Errai C D I Maven
Arch et yp e: "mvn sit e" will cau se maven h an g in g ( n o jaco co rep o rt )
The Errai Quickstart Guide contained various incorrect example commands. These
included the commands that generate Errai projects from Maven archetypes, and the
subsequent commands used to work with the generated projects. The example commands
have been fixed throughout the guide and their execution now produces expected results.
BZ#873593 - Eh an cemen t : Errai q u ickst art : Fo llo win g g u id e C h ap t er 3. Errai JAX- R S
Maven Arch et yp e: "mvn t est - Pin t eg rat io n - t est " p ro d u ces erro r o u t p u t
The AbstractErrai JaxrsT est test case, which is included in the jaxrs-q ui ckstart
Maven archetype, contained multiple subsequent IoC bootstrap calls. Consequently,
execution of the test produced errors, even though the test itself passed. The test case has
been modified so that only a single bootstrap call is performed. This fixed the issue and the
errors are no longer produced by the test.
BZ#877080 - Vio lat io n o f JSR - 29 9 in errai b u s serializ at io n d emo
Managed beans with public fields must be declared with the @ D epend ent scope to meet
§3.1 of the JSR-299 specification. Importing the bus-exampl es into JBoss D eveloper
Studio failed with an error, because the Seri al i zati o n bean included in the Errai busexampl es was not declared with the scope and contained the public cl i entEnd po i nt
field,. The cl i entEnd po i nt field has been changed from public to protected. This
eliminates the error and the examples can be imported successfully.
BZ#877117 - errai cd i st o ck d emo - b ad u rl o f t h e ap p licat io n
The errai -cd i -sto ck-d emo quickstart application contained the jbo ss-web. xml file,
which was left over from a different quickstart application and should not have been
included. Consequently, an incorrect URL was accessed when the applicaton was
deployed to a web server and displayed using the built-in browser in JBoss D eveloper
Studio. The leftover jbo ss-web. xml file has been removed, ensuring the application is
now accessed at the correct URL and displayed successfully.
H ib ern at e Search
BZ#878020 - H ib ern at e Search assemb ly f ails o n missin g f iles ( co p yrig h t .t xt an d
lg p l.t xt )
The Hibernate Search assembly descriptor referenced files that did not exist in the
distribution. As a consequence, Hibernate Search could not be built from source. This issue
has been fixed by including the referenced files in the distribution. As a result, Hibernate
Search can now be built from source successfully.
18
⁠Chapt er 6 . Fixed Issues
BZ#855948 - Field s d eclared o n @ Map p ed Su p erclass p aren t are n o t reco g n iz ed o n
ch ild en t it y b y p ro g rammat ic API map p in g
Programmatic API mapping does not recognize Hibernate Search fields inherited from
parent entities annotated with @ Mapped Supercl ass. As a consequence, Hibernate Search
views the fields as unmapped, resulting in a SearchExcepti o n. This is not considered a
bug, but a by-design behaviour that can only be addressed by a functionality
enhancement. Until the functionality is enhanced, the issue can be worked around by
overriding the getter methods of the inherited fields in the child entities.
R ich Faces
BZ#801048 - C o mp ilat io n o f In p u t U I co mp o n en t lo g s 2 erro rs ab o u t f acesco n f ig .xml
Compiling RichFaces UI components logs two errors related to the faces-co nfi g . xml
file. As the errors do not affect the functionality of the build, the issue is no longer
considered a bug and will not be addressed in the future releases.
BZ#822205 - R ich f aces kit ch en sin k arch et yp e - creat in g n ew memb er f ro m iPh o n e
cau ses b ro ken p u sh u p d at e o n mo b ile d evices
When creating a new member in the KitchenSink example application using a web browser
on an iOS device, the list of new members failed to get updated correctly. This occurred
even if a new member was subsequently added using a desktop-based web browser. The
underlying source code has been fixed and the member list is now updated correctly.
Seam
BZ#867815 - Seam2.3 C o n versat io n id n o t rest o red f ro m p ag e co n t ext
JSF2 partial state saving prevented Seam from properly initializing page context during
restore view phase. As a consequence, the conversation ID was not restored during the
restore view phase, which caused erroneous behaviour if a conversation-scoped
component was accessed during the phase. To fix this issue, Seam has been changed to
propagate conversation ID through the query string part of the URL. As a result, proper
conversation ID is now available during the restore view phase and conversation-scoped
components work properly even if accessed during the phase.
BZ#876999 - Seam2.3 remo t in g /ch at ro o m examp le d o esn ' t seem t o wo rk wit h 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 the
example works correctly in Internet Explorer 9.
Note
This was a known issue in the previous release and seems to have been resolved
now. However, the fix is not guaranteed.
BZ#877063 - Seam 2.3 seam- g en g en erat ed p ro ject is n o t t est ab le
The seam-g en SeamTest template was not properly migrated to Arquillian. As a
consequence, seam-g en tests did not work. To fix this issue, seam-g en SeamTest
template has been modified to properly use Arquillian. As a result of the fix, the tests
generated by seam-g en can now be run with ant test.
19
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
BZ#877082 - Seam 2.3, JB D S: EL co mp let io n d o esn ' t wo rk o n En t it yH o me o b ject s
JBoss D eveloper Studio could not find Enti tyHo me objects for autocompletion. As a
consequence, autocompletion for WebC o ntent did not work. This issue has been fixed in
JBoss D eveloper Studio 6.0.0.GA release and autocompletion now works correctly.
BZ#877374 - Seam2.3 s:cach e en ab led at t rib u t e is f alse b y d ef au lt
The s: cache element had an incorrect default value of fal se. As a consequence, caching
did not work by default. This has been fixed and the s: cache element has caching
enabled by default.
BZ#877414 - Seam2.3 s:valid at eEq u alit y req u ired at t rib u t e is f alse b y d ef au lt
( sh o u ld b e t ru e)
The s: val i d ateEq ual i ty element contained the req ui red attribute that had an
incorrect default value of fal se. As a consequence, this contrasted with the documentation
and previous behavior. This has been fixed and the default value of the req ui red attribute
is set to true.
BZ#877447 - Seam2.3 read me.t xt ref ers t o n o n - exist in g "d o c/ref eren ce/en - U S"
d irect o ry
The jbo ss-wfk-2. 1. 0 /jbo ss-seam-2. 3. 0 . Fi nal -red hat-1/read me. txt file
distributed with JBoss Web Framework Kit contained an invalid link to the community
documentation. This issue has been fixed.
BZ#878006 - Seam2.3 b lo g examp le u ses
o rg .h ib ern at e.search .erro rs.Emp t yQ u eryExcep t io n
The Seam blog example is configured to handle the exception
o rg . hi bernate. search. erro rs. EmptyQ ueryExcepti o n. This exception was not
present 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 only
stoplist tokens. This has been fixed by upgrading Hibernate Search to a version which
contains the o rg . hi bernate. search. erro rs. EmptyQ ueryExcepti o n. As a result, the
Seam blog example handles the exception
o rg . hi bernate. search. erro rs. EmptyQ ueryExcepti o n correctly.
BZ#876969 - Seam2.3 seam23mig rat io n .t xt ref ers t o co mmu n it y versio n s
The distributed seam23mi g rati o n. txt file contained outdated instructions. To fix this
issue, the seam23mi g rati o n. txt file has been updated with the correct information.
Secu rit y Issu es
BZ#512921 - ( C VE- 2009 - 26 25) C VE- 2009 - 26 25 xerces- j2, JD K : XML p arsin g D en ial- O f Service ( 6 84 5701)
Seam and RichFaces used the xerces: xercesImpl : 2. 9 . 1-patch0 1 artifact, which is
vulnerable to the CVE-2009-2625 denial-of-service flaw. The artifact has been replaced
with xerces: xercesImpl : 2. 9 . 1-red hat-3, which is no longer vulnerable to the
denial-of-service flaw.
Sn o wd ro p
BZ#820740 - Sn o wd ro p so u rces can n o t b e b u ilt o u t o f t h e b o x
Snowdrop sources could not be compiled out of the box because they required artifacts
20
⁠Chapt er 6 . Fixed Issues
that were not present in Maven Central nor in the Maven repositories distributed with JBoss
Web Framework Kit. To fix this issue, the dependencies on missing artifacts have been
updated to versions that are present in the JBoss Enterprise Application Platform 6.0.1
Maven 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.
Sp rin g
BZ#785684 - C o n su mers o f Sp rin g 3.0 an d 3.1 B O Ms mu st in clu d e WS C o o rd in at o r
wh en ru n n in g o n JB o ss En t erp rise Web Server
The 3.0, 3.1, and 3.2 versions of the Spring JBoss Stack (BOM file) distributed with JBoss
Web Framework Kit were previously compatible only with JBoss Enterprise Application
Platform. To use them with JBoss Enterprise Web Server, an additional dependency had to
be specified. The issue has been fixed and the JBoss Stacks are now compatible with
JBoss Enterprise Web Server out of the box.
BZ#796313 - Sp rin g R eso u rceAd ap t ers are n o t JC A 1.5 an d JC A 1.6 co mp lian t
The Spri ng C o ntextR eso urceAd apto r present in Spring versions tested with JBoss
Web Framework Kit 2.1.0 violated section 5.3.1 of the JCA 1.5 specification, and did not fully
implement JCA 1.5 and 1.6. Consequenly, deployment of RAR archives containing
packaged Spring files failed on JBoss Enterprise Application Platform. The issue has been
fixed in Spring 3.1.4.RELEASE and Spring 3.2.1.RELEASE, but Spring 3.0.7.RELEASE and
Spring 2.5.6.SEC03 are still affected. D escription of a workaround that allows successful
use of the affected versions has been included in Spring Installation Guide.
T icket Mo n st er
BZ#877086 - T icket Mo n st er: Valid at io n erro rs wh en imp o rt in g t o JB D S 5.0.1.G A
JavaScript validity errors were displayed after importing the TicketMonster example into
JBoss D eveloper Studio. Incorrect validation logic in JBoss D eveloper Studio caused this
error, but did not have any effect on the functionality of the example. A snippet that disables
JavaScript validation is now shipped with the example so that the errors are no longer
displayed.
T o rq u eB o x
BZ#874439 - Erro r wh en ru n n in g eap _o verlay scrip t wit h JR u b y 1.7.0.0 o n So laris
D ue to an issue in JRuby 1.7.0, execution of the to rq uebo x_eap_o verl ay. rb script
failed on machines running the Solaris operating systems. The issue has been fixed in
JRuby 1.7.3, which is the version tested with this release of JBoss Web Framework Kit, and
the script can now be executed successfully on all supported operating systems.
BZ#949947 - T o rq u eb o x - ArrayIn d exO u t O f B o u n d sExcep t io n d u rin g st art u p
When booting a TorqueBox server with multiple deployed applications, one of the
applications sometimes failed to get deployed with a
java. l ang . ArrayInd exO utO fBo und sExcepti o n,
java. l ang . Ind exO utO fBo und sExcepti o n, or an Appl i cati o n ro o t d o es no t
exi st error message followed by an incorrect path to one of the applications' root
directories. This was caused by a thread safety issue in the Ruby ERB library, through
which the contents of *-kno b. yml deployment descriptors are passed so that
21
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
environment variables and other expressions can be used inside the descriptors. To fix the
issue, TorqueBox was modified to pass in a new binding (execution context) whenever the
ERB library is used. As a result, TorqueBox servers with multiple deployed applications no
longer have some of those applications randomly fail to deploy.
Q u ickst art s
BZ#877311 - Erro rs in ' examp le- wf k- set t in g s.xml' in JB o ss WFK Q u ickst art s
The setti ng s-wfk-exampl e. xml file distributed as a part of the JBoss Web Framework
Kit quickstart applications specified a mirror element that resulted in non-resolvable JBoss
Web Framework Kit artifacts. This issue has been fixed by not using the mirror element in
the setti ng s-wfk-exampl e. xml file. As a result, the Boss Web Framework Kit artifacts
are resolved appropriately.
22
⁠Chapt er 7 . Known Issues
Chapter 7. Known Issues
The following issues are known to be present in JBoss Web Framework Kit 2.2.0:
Arq u illian
BZ#875031 - D ead lo ck co n d it io n in T arG Z h an d lin g
The ShrinkWrap T arG zExpo rter implementation contains a race condition which can
result in a deadlock while exporting an archive to a tar. g z file. This bug is still under
investigation. As a workaround, use the Z IP-based implementation to import or export files
with ShrinkWrap, instead of the tar. g z implementation. The Z IP-based implementation is
known to work on all platforms.
BZ#881017 - Arq u illian AS7 7.1.1.Fin al ad ap t o r d o es n o t wo rk wit h jmx p ro t o co l wit h
EAP 6 .0.1
The OSGi layer, which was present but disabled in JBoss Enterprise Application Platform
6.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
<d efaul tP ro to co l type= "Servl et 3. 0 "/> under the <arq ui l l i an> element in the
arq ui l l i an. xml file. Then add the following servlet dependency to your project's
po m. xml file:
​< dependency>
​
<groupId>org.jboss.arquillian.protocol</groupId>
​
<artifactId>arquillian-protocol-servlet</artifactId>
​
<scope>test</scope>
​< /dependency>
Errai
BZ#865415 - Errai: d ep lo ymen t o f t h e errai- jp a- d emo - b asic examp le lo g s g u ava
relat ed erro rs
Errai requires version 12.0 or newer of the Google Guava library, but JBoss Web
Framework Kit and JBoss Enterprise Application Platform have standardized on version
11.0. The po m. xml descriptor for the Errai examples have been modified to use Google
Guava version 12.0 at compile time, since it is strictly required. In runtime, the examples use
version 11.0.
D ue to this behavior, the following error appears in the console log when either of the Errai
JPA examples are deployed:
ERROR [stderr] (MSC service thread 1-4)
java.util.concurrent.ExecutionException:
java.lang.NoSuchMethodError:
com.google.common.util.concurrent.MoreExecutors.sameThreadExecuto
r()Lcom/google/common/util/concurrent/ListeningExecutorService;
The appearance of this error is expected and can be disregarded.
BZ#883918 - Errai is n o t co mp at ib le wit h G WT 2.5.0
23
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
D ue to changes introduced in Google Web Toolkit 2.5.0, compiling Errai with GWT 2.5.0
fails with errors related to the UIBi nd er class. It is therefore not recommended to use Errai
with GWT 2.5.0, even if GWT is used only as a runtime. However, please note that GWT
2.4.0 exposes a cross-site scripting (XSS) flaw identified by CVE-2012-5920. No
workaround for this flaw is currently known. The flaw will be addressed in a future release of
Errai.
BZ#921049 - Errai K it ch en Sin k Maven Arch et yp e 2.2.1- SN APSH O T - valid at io n erro r
in G WT d evelo p men t mo d e
Compiling a project generated from the Errai Kitchen Sink Maven archetype using GWT
Maven Plugin fails with all versions of OpenJD K 7 and Oracle JD K 7 update 16 or earlier.
To work around the issue, compile the project with any version of Oracle JD K 6 or
OpenJD K 6, or Oracle JD K 7 update 17 or later. The compiled project can then be deployed
with any JD K.
G en eral Issu es
BZ#870349 - G u ava versio n s in Errai an d R ich Faces are n o t co mp at ib le
RichFaces and Errai are both included components in JBoss Web Framework Kit, and each
uses a different version of Google Guava. As a result, when they are used together in the
same 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, you
can add the following XML to your Maven po m. 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 - Imp o rt ed D elt asp ike B ean man ag er q u ickst art sh o ws a warn in g in JB D S
6
After importing the deltaspike-beanmanagerprovider quickstart application into JBoss
D eveloper Studio 6, a JPA module is detected, but is not configured because no JPA
connection 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 around
by disabling JPA validation. To disable JPA validation, right-click the application in Project
24
⁠Chapt er 7 . Known Issues
Explorer, choose P ro perti es from the context menu, select Val i d ati o n in the displayed
window, enable the Enabl e project specific settings option, and uncheck the two boxes in
the JP A Val i d ato r line.
BZ#913165 - R ep eat : in p u t in sid e rep eat in n o t u p d at ed
The i nput HTML element rendered by the h: i nputT ext JSF component does not contain
the val ue attribute. Consequently, when entering text in the input field, submitting it and
trying to clear the input text by clearing the bound value on the server side, the received
partial update does not clear the input field in the browser.
The issue originates in Mojarra 2.1.13, which is included in JBoss Enterprise Application
Platform 6.0.1. JBoss Enterprise Application Platform 6.0.0 is not affected by this issue as it
contains a different version of Mojarra. No workaround for this issues is currently known.
BZ#790873 - G rails ap p licat io n s can n o t b e d ep lo yed t o EAP u n less O SG i is d isab led
OSGi is not enabled in JBoss Enterprise Application Platform 6. Artifacts produced by
Grails miss a P ackag e-Impo rt of javax. nami ng in the bundle. The workaround for this
issue is to disable OSGi while packaging your Grails applications. You can do this using
the following configuration in the Bui l d C o nfi g . g ro o vy configuration file:
grails.project.war.osgi.headers = false
G o o g le Web T o o lkit
BZ#803780 - Wro n g p o p u p b eh avio r in G WT o n iO S d evices
iPad and iPhone devices ignore single-tap events outside pop-up elements, which
subsequently do not disappear when users tap outside the element area. With the Imag e
element, you can work around the issue with a single tap directly on the image. With the
D ate P i cker element, picking a date makes it disappear. With the Si mpl e T ext Area,
you can work around the issue by activating a different element on the page. With all other
elements, the workaround is to navigate to a different page and then back.
BZ#803782 - G WT : U n ab le t o ed it t ext in sid e o f R ich T ext Area elemen t o n mo b ile
d evices
Some iOS and Android devices treat R i chT extArea as a read-only HTML element.
Consequently, the devices fail to activate the R i chT extArea and write text into it. The
workaround is to avoid using R i chT extArea elements in applications accessed by mobile
devices. Other HTML elements are not affected by this issue.
BZ#919447 - G WT f ails o n IB M Java 1.6 an d 1.7
Google Web Toolkit attempts to load pre-compiled GWT module archives (. g wtar files) to
increase performance. Consequently, building GWT examples shipped with this release
fails with the IBM implementations of the Java D evelopement Kit (both 1.6 and 1.7). To work
around the issue, use the -D g wt. usearchi ves= fal se parameter with g wt-mavenpl ug i n to disable loading of the pre-compiled archives.
R ich Faces
BZ#802444 - R ich Faces Sh o wcase - JMS Pu sh : H o rn et Q JMS co n n ect io n is secu red
b y d ef au lt
The default installation of JBoss Enterprise Application Platform and JMS Push, which is
required by the RichFaces Showcase example, are secured. To deploy the application, you
25
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
need to add a new user to the ApplicationRealm using the $JBO SS_HO ME/bi n/ad d user. bat or ad d -user. sh script, with the guest role. Then modify the web. xml file in the
RichFaces Showcase and replace ${username} and ${passwo rd } with the actual
credentials. The XML containing the two replaceable values is shown below.
​< context-param>
​ <param-name>org.richfaces.push.jms.connectionUsername</paramname>
​ <param-value>${username}</param-value>
​< /context-param>
​< context-param>
​ <param-name>org.richfaces.push.jms.connectionPassword</paramname>
​ <param-value>${password}</param-value>
​< /context-param>
After adding the user to the ApplicationRealm and adding the credentials to the
applications's web. xml , the application will work correctly.
BZ#822210 - R ich f aces kit ch en sin k arch et yp e - it sh o u ld b e p o ssib le t o ret u rn f ro m
viewin g d et ails ab o u t memb er b ack t o t h e list o f all memb ers o n mo b ile d evices
The browser interface of the KitchenSink example application does not include a link or
navigation button to allow you to return from the D etai l s view to the Li st view on mobile
devices. To work around this limitation, use the Ho me button, then click the Li st o f
P eo pl e link.
BZ#952235 - a4 j:p u sh co mp o n en t R ich Faces b ackward co mp at ib ilit y p ro b lem
Applications created with RichFaces 4.2.3.Final, which is the version shipped with JBoss
Web Framework Kit 2.1.0, contain a dependency on the 0.8.4 version of the Atmosphere
framework, which is not backward compatible with RichFaces 4.3.1.Final shipped with this
release. Consequently, the a4 j: push component does not provide any push updates
when the application is used with RichFaces 4.3.1.Final. To work around the issue, change
the Atmosphere depencency to version 1. 0 . 10 , or replace the Atmosphere libraries with
the respective versions. As a result of the workaround, the a4 j: push component provides
push updates correctly.
Seam
BZ#867381 - Seam2.3 seam- g en g en erat ed act io n sh o ws "T h e f o rm co mp o n en t
n eed s t o h ave a U IFo rm in it s an cest ry. ..." messag e
On submitting a JSF request, a JSF warning message is displayed. As a workaround for
this issue, use the P R O D UC T IO N value for javax. faces. P R O JEC T _ST AG E in web. xml
as 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
⁠Chapt er 7 . Known Issues
BZ#875614 - Seam2.3 sp o rad ic N PE in
o rg .jb o ss.seam.jms.T o p icSessio n .creat e( T o p icSessio n .java:38)
By design, Seam puts newly instantiated components into the scopes before calling the
@ C reate or @ P o stC o nstruct methods. The T o pi cC o nnecti o n and
Q ueueC o nnecti o n Seam JMS components do not synchronize access to their @ C reate
and @ Unwrap methods. This causes multiple concurrent requests that are the first to require
these components to inject instances of these built-in application-scoped components
before they are instantiated.
To work around this issue, you can force the components to be created during application
start-up. In this case, there is no risk of this race condition occurring. The following
example code shows how to apply this work-around:
​@ Name("topicConnectionStartup")
​@ Startup
​@ Scope(ScopeType.APPLICATION)
​p ublic 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 and
no race condition occurs.
BZ#875656 - XML valid at io n erro rs af t er imp o rt in g B lo g examp le t o JB D S
After importing the Maven Blog example into JBoss D eveloper Studio, the following three
errors are displayed:
cvc-elt.1: Cannot find the declaration of element 'f:view'.
Referenced file contains errors (file:/jbdevstudio6.0.0.Beta1/studio/plugins/org.jboss.tools.jst.web.kb_3.4.0.Beta1v20121018-0628-B39/taglibs/tld/facelets_jsf_core.taglib.xml).
Referenced file contains errors (file:/jbdevstudio6.0.0.Beta1/studio/plugins/org.jboss.tools.jst.web.kb_3.4.0.Beta1v20121018-0628-B39/taglibs/tld/html_basic.taglib.xml).
Currently, there is no workaround for this issue.
BZ#878496 - Fo r Seam 2.3 seam- g en g en erat ed p ro ject , JB D S rep o rt s missin g f iles
ref eren ced f ro m view- id in p ag es.xml
When a seam-g en generated project is imported into JBoss D eveloper Studio, the project
configuration is insufficient to correctly supply and validate the Seam pag es. xml file. As a
consequence, JBD S 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 P ro ject
pro perti es, go to P ro ject Facets and choose Seam, D ynami c Web pro ject, and
the Java Server Faces options.
27
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
BZ#878505 - In Seam 2.3 seam- g en g en erat ed p ro ject imp o rt ed in JB D S, EL
co mp let io n f o r Seam Messag es d o esn ' t wo rk
When a seam-g en generated project is imported into JBoss D eveloper Studio, the project
configuration is insufficient to correctly supply and validate Seam Messages properties
used in pag es. xml or messag es. pro perti es. As a consequence, JBoss D eveloper
Studio 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 P ro ject
pro perti es, go to P ro ject Facets and choose Seam, D ynami c Web pro ject, and
the Java Server Faces options.
BZ#912394 - Seam2.3 C o mp o n en t s in clu d ed wit h u i:in clu d e src= "#
{p ag eSco p ed ViewId } b ro ken
Inserting a page-scoped UI view component into facelet fragment does not work due to JSF
design issue in partial restore processing. As a consequence, you cannot use page scope
UI view components with the <ui : i ncl ud e> tag. As a workaround for this issue, disable
P AR T IAL_ST AT E_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 vi ewId , which requires
P ag eSco pe vi ewID components, and partial state saving mode does not work for it.
​< context-param>
​
<param-name>javax.faces.FULL_STATE_SAVING_VIEW_IDS</paramname>
​
<paramvalue>/index.xhtml,/component1.xhtml,/component2.xhtml</paramvalue>
​< /context-param>
As a result of the workaround, you can use a page-scoped UI view component.
BZ#916998 - Seam2.3 seam- g en ivy b ro ken
Seam-gen generated project cannot use maven dependency management through ivy. As a
result, you cannot use the seam-g en command seam ad d -i vy. Currently, there is no
workaround for this issue.
BZ#922049 - seam2.3 seam- g en reso u rces- t est /arq u illian .xml n o t u sed
In Seam 2.3, the reso urces-test/arq ui l l i an. xml configuration file is not used when
running ant test. To use the Arquillian configuration specified in the file, move the
configuration file to the root of your generated project.
BZ#922059 - seamsp ace examp le o ccasio n ally f ails wit h a n p e o n ib m jvm
28
⁠Chapt er 7 . Known Issues
On IBM virtual machines, the seamspace example fails with a Nul l P o i nterExcepti o n
while submitting a new blog entry. This issue is caused by an issue in the IBM virtual
machines. The fix for this issue has been deferred until a fix to the IBM virtual machines is
introduced.
BZ#876999 - Seam2.3 remo t in g /ch at ro o m examp le d o esn ' t seem t o wo rk wit h IE 9
The Seam 2.3 chat room example does not work correctly when executed in Internet
Explorer 9. Instead, the example displays JavaScript errors. As a workaround, use a
different version of Internet Explorer or an alternative Internet browser.
Note
This was a known issue in the previous release and seems to have been resolved
now. However, the fix is not guaranteed.
BZ#869638 - Seam2.3: T AG - 16 G ro o vyb o o kin g examp le
The Seam groovybooking example uses the maven-antrun-pl ug i n, which cannot be
imported into JBoss D eveloper Studio automatically. As a consequence, the example
cannot be built automatically in JBoss D eveloper Studio. As a workaround, use the mvn
cl ean packag e Maven command to build the example.
BZ#902905 - Seam2.3 @ D at aMo d el & @ D at aMo d elSelect io n d o esn ' t wo rk wit h
rich f aces4 d at aT ab le
The UID ataT abl e component (the <ri ch: d ataT abl e> element) shipped with RichFaces
4 does not extend the JSF UID ata class. As a consequence, rendering of Seam
components annotated with @ D ataMo d el and @ D ataMo d el Sel ecti o n inside a
UID ataT abl e does not work as expected. To work around the issue, use the JSF
D ataT abl e (the <h: d ataT abl e> element) instead of the Richfaces UID ataT abl e.
BZ#950929 - Seam2.3 seam- g en g en erat ed p ro ject s are missin g so me lib /t est s
lib raries
The . cl asspath files of projects generated by seam-g en do not get updated after the
following JAR archives are removed:
l i b/test/jbo ss-remo ti ng -3. 2. 13. G A-red hat-1. jar
l i b/test/xni o -api -3. 0 . 3. G A. jar
l i b/test/xni o -ni o -3. 0 . 3. G A. jar
Errors about missing library JARs are consequently displayed in JBoss D eveloper Studio.
To work around the issue, remove the JARs from build classpath manually: go to project
Pro p ert ies → B u ild Pat h → C o n f ig u re B u ild Pat h → Lib raries, select the JARs and
click the R emo ve button. As a result of the workaround, the errors will no longer be
displayed.
BZ#951044 - Seam2.3 seam- g en EAR p ro ject exp lo d e t arg et t o u ch es .d o d ep lo y
f o rcin g a rest art , p reven t in g h o t - d ep lo ymen t
The Ant bui l d . xml file of an EAR application generated by seam-g en contains an error
that influences the logic used to determine if the deployed application should be restarted
after being updated. As a consequence, the application is always restarted, even in cases
where hot deployment would normally be performed. To work around the issue, replace the
29
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
following part of the bui l d . 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 in
relevant cases, and hot deployment will be performed otherwise.
BZ#951540 - Seam2.3 B O M sh o u ld n o t d eclare jb o ss- as- arq u illian - co n t ain er{man ag ed |remo t e} versio n
D uplicated jbo ss-as-arq ui l l i an-co ntai ner-manag ed and jbo ss-asarq ui l l i an-co ntai ner-manag ed -remo te artifacts are defined in the
d epend encyManag ement section of the Seam JBoss Stack, causing incorrect versions to
be used. To work around the issue, specify the o rg . jbo ss. bo m: jbo ss-javaee-6 . 0 wi th-to o l s: 1. 0 . 4 . Fi nal -red hat-wfk-1 JBoss Stack before importing the Seam
JBoss Stack. As a result of the workaround, d epend encyManag ement entries from the
jbo ss-javaee-6 . 0 -wi th-to o l s JBoss Stack will be detected by Maven first, and the
duplicated artifacts and their versions will not be taken into account.
BZ#903177 - Seam2.3 lo caliz at io n set t in g s via co mp o n en t .xml d o esn ' t wo rk
When l o cal e-co nfi g 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, l o cal e-co nfi g configuration is not taken into account in the
application. The issue can be worked around by using the
co m. sun. faces. co nfi g . C o nfi g ureLi stener configuration in the application's
web. xml file. As a result of the workaround, the locale configuration works as expected.
BZ#928002 - Seam2.3 p ag es rewrit e d o esn ' t rewrit e s:lin k p arams
Using the <rewri te> configuration in the Seam co mpo nents. xml file does not ensure
correct URL rewriting. Because URL rewriting is performed before parameters are set, URLs
produced by the <s: l i nk> and <s: butto n> elements are rendered with query string
parameters. No workaround for this issue is currently known.
BZ#921660 - Seam2.3 SeamViewH an d ler ad d s co n versat io n id even if co n versat io n is
n o t lo n g ru n n in g
Seam redirect URLs always contain the ci d querystring parameter specifying a
conversation ID , even in cases where long running conversations do not take place. No
workaround for this issue is currently known.
30
⁠Chapt er 7 . Known Issues
BZ#921878 - Seam2.3 seam- g en N C D FE o rg .slf 4 j.imp l.St at icLo g g erB in d er o n IB M
JVM
Running seam g enerate 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-g en on IBM Java Virtual Machines. No workaround for this issue is currently known.
BZ#948265 - Seam2.3 SeamIn t ercep t o r d o esn ' t wo rk o n EJB @ Sch ed u le met h o d s
Seam does not implement support for EJB 3.1 timers. As a consequence, features like Seam
bijection do not work with EJB 3.1 timers. To work around this issue, timeout methods can
use Li fecycl e. beg i nC al l () and Li fecycl e. end C al l () methods for each timeout
invocation, and use the C o mpo nent. g etInstance() method to get instances of
application-scoped components.
BZ#948215 - Seam2.3 javax.n amin g .N ameN o t Fo u n d Excep t io n t ryin g t o call EJB Seam
co mp o n en t s f ro m q u art z asyn ch ro n o u s met h o d s
Calling EJB Seam components from non-EJB threads (for example asynchronous Quartz
threads) does not work due to a different implementation of the JND I pattern specification in
Java EE 6. As a consequence, the javax. nami ng . NameNo tFo und Excepti o n exception
is generated while looking for EJB components from a non-EJB thread. The workaround for
this issue is actually the correct method of accessing EJB components: accessing EJB
components from non-EJB threads by global JND I and not by application JND I.
BZ#952571 - Seam p ro d u ces malf o rmed p art ial resp o n se o n ViewExp ired Excep t io n
wit h Ajax
The parti al -respo nse elements in AJAX responses produced by Seam are duplicated.
Consequently, redirection rules defined in the pag es. xml file are not correctly processed
and therefore not followed. No workaround for this issue is currently known.
Secu rit y Issu es
BZ#873317 - ( C VE- 2012- 5783) C VE- 2012- 5783 jakart a- co mmo n s- h t t p clien t : missin g
co n n ect io n h o st n ame ch eck ag ain st X.509 cert if icat e n ame
Apache Commons HttpClient 3 is vulnerable to CVE-2012-5783, a security flaw related to
incorrect validation of X.509 certificates. HttpClient 3 has reached its end of life as a
component maintained by Apache, and no upstream build is available that addresses this
flaw. The version of HttpClient 3 that is shipped with JBoss Web Framework Kit 2.2.0 has
been built by Red Hat and includes a patch for this flaw. HttpClient 3 versions consumed
from Maven Central do not have this patch applied. Apache Commons HttpClient 3 is a
transitive 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.
Sn o wd ro p
BZ#948702 - Sp o rt sclu b : In vo ice g en erat io n f ails f o r acco u n t wit h b illin g t yp e
SEMIMO N T H LY
The SEMIMO NT HLY billing type is not implemented in the
o rg . jbo ss. sno wd ro p. sampl es. spo rtscl ub. d o mai n. enti ty. Acco unt class of
31
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
the Sportsclub example. Consequently, generating an invoice for a subscription that has
the SEMIMO NT HLY billing type set fails with an Il l eg al Arg umentExcepti o n. No
workaround for this issue is currently known except for extending the implementation by
your own means.
Sp rin g
BZ#760115 - R ich Faces wit h Sp rin g Web Flo w req u ires ad d it io n al co n f ig u rat io n
If you need to use Spring WebFlow 2.3 and RichFaces 4 together, you need to create an
extra bean to resolve RichFace resources. This bean is not automatically included as part
of faces: reso urces. 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 fl o wMappi ng so that RichFaces has
higher priority than the user-generated flow (lower numbers get higher priority), and add the
following bean to your application:
​< bean name="richfacesResourceHandler"
​c lass="org.springframework.faces.webflow.JsfResourceRequestHandler"
/>
​< bean
class="org.springframework.web.servlet.handler.SimpleUrlHandlerMap
ping">
​ <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 - Sp rin g SAAJ su p p o rt t o g et h er wit h Su n /O racle SAAJ imp lemen t at io n
d o esn ' t wo rk o n IB M JVMs o u t o f t h e b o x
The Oracle SAAJ implementation uses internal JD K classes that are not provided with IBM
JD Ks. This causes compilation errors in applications using Spring SAAJ support together
with the Oracle SAAJ implementation and an IBM JD K.
The recommended workaround is to remove Oracle SAAJ JARs from the class path of your
application so that the bundled IBM implementation is used instead. The following is an
example 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 Oracle
JAXP implementation to the class path:
32
⁠Chapt er 7 . Known Issues
​< dependency>
​ <groupId>com.sun.xml.parsers</groupId>
​ <artifactId>jaxp-ri</artifactId>
​ <version>1.4.5</version>
​< /dependency>
BZ#916903 - Sp rin g R o o 1.2.3.R ELEASE d o es n o t wo rk wit h Sp rin g 3.2.1.R ELEASE
o u t o f t h e b o x d u e t o missin g sp rin g - web d ep en d en cy
Spring Roo 1.2.3 uses Spring Core 3.2.0, whose package structure is different from Spring
Core 3.2.1. As a consequence, configuring an application generated by Spring Roo to use
the Spring JBoss Stack distributed with JBoss Web Framework Kit causes compilation
errors. To work around this issue and compile the application successfully, add the
following dependency to your project:
​< dependency>
​ <groupId>org.springframework</groupId>
​ <artifactId>spring-web</artifactId>
​ <version>3.2.1.RELEASE</version>
​< /dependency>
BZ#923377 - Sp rin g ' s g et t in g - st art ed examp le sh o ws warn in g s af t er imp o rt in g in t o
JB D S 6
When the Spring getting-started example is imported into JBoss D eveloper Studio, various
warnings are reported. To remove the warnings, add the missing </tabl e> tag before the
</fo rm> tag in the src/mai n/webapp/WEB-INF/vi ews/g reet. jsp file. Other
warnings can be removed by editing the src/mai n/webapp/i nd ex. jsp file and adding
<head ><meta HT T P -EQ UIV= "R EFR ESH" co ntent= "0 ; url = app/g reet"></head >
right after the <html > tag, and also removing the <h2> element with all its content.
BZ#801406 - In valid p ersist en t .xml d escrip t o r in t h e Pet clin ic examp le
When importing the Petclinic example application into JBoss D eveloper Studio 6, a
persi stence. xml file with invalid contents is created in the
src/mai n/reso urces/MET A-INF/ directory. D uring deployment, this file has higher
priority than the correct src/mai n/envi ro nments/eap/reso urces/MET AINF/persi stence. xml file, and the deployment fails. To work around the issue, remove
the invalid src/mai n/reso urces/MET A-INF/persi stence. xml file before deploying
the application.
St ru t s
BZ#803749 - St ru t s 1 Sh o wcase ap p licat io n ' s JSF in t eg rat io n d o es n o t wo rk o n
EAP6
The JSF integration in the Struts 1 Showcase application is not functional with 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-
33
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
name>
​
<param-value>true</param-value>
​< /context-param>
BZ#803747 - St ru t s 2 Sh o wcase ap p licat io n ' s JSF in t eg rat io n d o es n o t wo rk o n
EAP6
The JSF integration in the Struts 2 Showcase application is not functional with 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</paramname>
​
<param-value>true</param-value>
​< /context-param>
BZ#803860 - St ru t s 2 ap p licat io n wit h o u t st ru t s.xml f ails t o d ep lo y o n EAP6
A Struts 2 application without the struts. xml descriptor can be deployed on JBoss
Enterprise Application Platform 6, but actions are not properly mapped. There is no known
workaround for this issue other then including the struts. xml file in your application.
T icket Mo n st er
BZ#879576 - T icket - mo n st er d emo d o es n o t wo rk in IE10 p ro p erly
JavaScript libraries used in the TicketMonster example are not compatible with Internet
Explorer 10. Consequently, some pages of the example website are not rendered at all when
accessed using Internet Explorer 10. To work around this issue, enable the browser's
compatibility mode or use an alternative browser.
BZ#871099 - T icket Mo n st er: g en erat ed Ad min ist rat io in sect io n d o es n o t wo rk
p ro p erly
Multiple issues occur in the Ad mi ni strati o n section of the TicketMonster example when
it is generated using JBoss Forge. The root cause of the issue is in the implementation of
JBoss Forge and not in the TicketMonster example. No workaround for this issue is
currently known.
BZ#950334 - T icket Mo n st er: rich f aces- b o m versio n d o es n o t alig n wit h WFK
RichFaces Plugin for JBoss Forge does not use the RichFaces version distributed with
JBoss Web Framework Kit 2.2.0. Consequently, the Administration section of the
TicketMonster example uses RichFaces 4.2.2. To work around the issue, perform the
following changes in the project's po m. 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
⁠Chapt er 7 . Known Issues
​
<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>
​ <!-- delete this line --><version>4.2.2.Final</version>
​< /dependency>
​< dependency>
​ <groupId>org.richfaces.core</groupId>
​ <artifactId>richfaces-core-impl</artifactId>
​ <!-- delete this line --><version>4.2.2.Final</version>
​< /dependency>
As a result of the workaround, the implementation of the Administration section will use the
correct version of RichFaces.
BZ#929102 - T icket Mo n st er: rich f aces- b o m can ' t b e f o u n d d u rin g Ad min ist rat io n
sect io n g en erat io n
A bug in JBoss Forge causes the following error when downloading the RichFaces JBoss
Stack with the JBoss Web Framework Kit Maven repository enabled in the
acti veP ro fi l es section of the setti ng s. 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 veri fy goal from
the JBoss Forge console.
BZ#953566 - So me o f p erf o rman ce d at es h ave p assed so t h e p erf o rman ces are n o t
sh o wn in `Mo n it o r` sect io n
The sample performances in the TicketMonster example have their dates set to April and
35
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
May 2013. Consequently, no performances will be displayed in the Mo n it o rin g section of
the example after these dates. To work around the issue, change the dates manually via
h2console, in the Ad min ist rat io n section of the example, or directly in the ti cketmo nster/d emo /src/mai n/reso urces/i mpo rt. sq l query. As a result, the
performances will be displayed until the newly set dates.
T o rq u eB o x
BZ#915749 - D o cu men t t h at JR u b y 1.6 .8 su p p o rt is d ro p p ed f o r T o rq u eB o x
Using JRuby 1.6.8 to run the TorqueBox distribution shipped with this release of JBoss
Web Framework Kit is no longer tested. JRuby 1.7.3 is the only JRuby version tested with
this release.
BZ#876119 - B u n d ler u ses wro n g g em versio n wh en G emf ile sp ecif ies ~ >
x.x.x.red h at .1
The Bundler gem used in Gemfile for specifying Torquebox versions has had its behavior
modified, causing the ~ > operator to not correctly resolve the . red hat. X gem variant. To
work around this issue, specify the exact TorqueBox productized gem version within the
Gemfile.
36
⁠Chapt er 8 . Product Support and License Websit e Links
Chapter 8. Product Support and License Website Links
Pro d u ct Pag e
http://www.redhat.com/products/jbossenterprisemiddleware/web-framework-kit/
Su p p o rt Pro cesses
http://www.redhat.com/support/process/
Pro d u ct Su p p o rt Sco p e o f C o verag e
https://access.redhat.com/support/offerings/production/soc.html
Pro d u ct io n Su p p o rt Service Level Ag reemen t
https://access.redhat.com/support/offerings/production/sla.html
D evelo p er Su p p o rt Sco p e o f C o verag e
https://access.redhat.com/support/offerings/developer/soc.html
D evelo p er Su p p o rt Service Level Ag reemen t
https://access.redhat.com/support/offerings/developer/sla.html
Pro d u ct U p d at e an d Su p p o rt Po licy b y Pro d u ct
http://www.redhat.com/security/updates/jboss_notes/
JB o ss En d U ser Licen se Ag reemen t
http://www.redhat.com/licenses/jboss_eula.html
37
Red Hat JBoss Web Framework Kit 2 .2 2 .2 .0 Release Not es
Revision History
R evisio n 1- 2
WFKD OC-100: Fixed typo
Wed N o v 05 2014
R evisio n 1- 1
T u e Ap r 23 2013
Published with the release of JBoss Web Framework Kit 2.2.0.
38
Mich elle Mu rray
Pet r Pen icka