Back to bug 769022

Who When What Removed Added
Karel Piwko 2011-12-19 17:11:13 UTC Summary EWS Hibernate causes security check failure when combined with RichFaces EWS Hibernate 3.3 causes security check failure when combined with RichFaces 3.3
Karel Piwko 2011-12-19 17:11:25 UTC CC rebecca.jboss
Rebecca Newton 2012-01-11 23:32:41 UTC CC rnewton
Karel Piwko 2012-01-12 07:31:55 UTC Environment EWS 1.0.2.CR3 EWS 1.0.2
Marius Bogoevici 2012-04-12 20:29:19 UTC Status NEW ON_DEV
Marek Novotny 2012-04-27 12:43:29 UTC Status ON_DEV ON_QA
Target Release --- 2.0.0.ER5
CC mnovotny
Karel Piwko 2012-05-21 15:00:26 UTC Status ON_QA MODIFIED
Assignee mariusb rnewton
QA Contact kpiwko
Karel Piwko 2012-05-22 12:19:26 UTC Target Release 2.0.0.ER5 2.0.0.GA
Karel Piwko 2012-06-01 12:43:40 UTC Status MODIFIED VERIFIED
Karel Piwko 2012-06-22 07:59:05 UTC Status VERIFIED ASSIGNED
Target Release 2.0.0.GA ---
Rebecca Newton 2012-08-07 04:16:38 UTC Assignee rnewton irooskov
Karel Piwko 2012-09-24 13:44:30 UTC Target Release --- 2.1.0
Karel Piwko 2012-09-24 13:44:53 UTC CC rnewton irooskov
mark yarborough 2012-11-12 15:03:27 UTC Target Release 2.1.0 2.2.0
CC myarboro
Isaac Rooskov 2012-11-15 03:40:50 UTC Doc Text Packaging Hibernate 3.3 and RichFaces 3.3 libraries in an
application using Enterprise Web Server causes the security check to fail due
to a combination of signed and unsigned jars. This is because the Hibernate
jars in Enterprise Web Server come signed, and Hibernate has a transitive
dependency on commons-collections. RichFaces has a transitive dependency on
commons-collections and commons-digester, but transitive dependencies are not
shipped. The workaround for this issue is to use the community version of
commons-collections within an application that also uses RichFaces.
Packaging Hibernate 3.3 and RichFaces 3.3 libraries in an
application using JBoss Enterprise Web Server causes the security check to fail. This is due
to a combination of signed and unsigned jars. This is because the Hibernate
JAR files in Enterprise Web Server come signed, and both Hibernate and RichFaces have a transitive
dependency on the package: commons-collections which is not shipped.

The workaround for this issue is to use the community version of
commons-collections within a Hibernate application that also uses RichFaces.
Petr Penicka 2013-01-17 15:15:59 UTC CC ppenicka
Assignee irooskov wfk-docs
mark yarborough 2013-02-28 12:57:39 UTC CC lpearce
Assignee wfk-docs lpearce
Target Release 2.2.0 2.3.0
Karel Piwko 2013-02-28 15:30:26 UTC Status ASSIGNED CLOSED
Resolution --- DEFERRED
Assignee lpearce ppenicka
Last Closed 2013-02-28 10:30:26 UTC
John Skeoch 2014-01-13 00:23:50 UTC CC dhensley
Douglas Silas 2014-01-13 08:40:19 UTC CC dhensley

Back to bug 769022