| Summary: | EWS Hibernate 3.3 causes security check failure when combined with RichFaces 3.3 | ||
|---|---|---|---|
| Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | Karel Piwko <kpiwko> |
| Component: | Spring | Assignee: | Petr Penicka <ppenicka> |
| Status: | CLOSED DEFERRED | QA Contact: | Karel Piwko <kpiwko> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 2.0.0.DR06 | CC: | irooskov, lpearce, mnovotny, myarboro, ppenicka |
| Target Milestone: | --- | ||
| Target Release: | 2.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/JBWFK-109 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
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.
|
Story Points: | --- |
| Clone Of: | 724747 | Environment: |
EWS 1.0.2
|
| Last Closed: | 2013-02-28 15:30:26 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 724747 | ||
| Bug Blocks: | |||
|
Description
Karel Piwko
2011-12-19 17:08:54 UTC
Caused by following class present in both commons-collections and commons-beanutils, which one of them is signed: org.apache.commons.collections.ArrayStack commons-beanutils-1.7.0.jar , commons-beanutils-1.8.0.jar , commons-collections-2.1.1.jar , commons-collections-3.1-wfk-4.jar , commons-collections-3.1.jar , commons-collections-3.2.1.jar , commons-collections-3.2.jar
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Packaging Hibernate and RichFaces 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.
Agree on technical note Modified release notes text.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,4 +1,4 @@
-Packaging Hibernate and RichFaces libraries in an
+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
I'm closing this issue as DEFERRED because it affects WFK 1.2 to WFK 2.0 migration. There is no delivery channel for WFK 2.2 to fix that issue. |