| Summary: | Hibernate 3.3 causes security check failure when combined with Spring Roo | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | Tomas Repel <trepel> | ||||
| Component: | Spring | Assignee: | Marius Bogoevici <mariusb> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Tomas Repel <trepel> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 2.0.0.ER3 | CC: | irooskov, kpiwko, mnovotny, rruss | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 2.1.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Packaging Hibernate 3.3 and Spring Roo libraries in an
application 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.
Spring Roo uses Struts Tiles, an artifact that has a transitive dependency on commons-beanutils, which is unsigned and contains same classes as commons-collections.
The workaround for this issue is to use the community or unsigned version of commons-collections within an application that also uses Spring Roo.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-10-22 12:11:45 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: | |||||
| Attachments: |
|
||||||
|
Description
Tomas Repel
2012-03-28 08:40:06 UTC
Suggestion - rework the technical note from 769022 to include this case.
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 3.3 and Spring Roo libraries in an
application 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.
Spring Roo uses Struts Tiles, an artifact that has a transitive dependency on commons-beanutils, which is unsigned and contains same classes as commons-collections.
The workaround for this issue is to use the community or unsigned version of commons-collections within an application that also uses Spring Roo.
Spring Roo 1.0.x, which supports JPA1/Hibernate 3.3 is no longer supported in WFK 2.1.0. Newer versions of Spring Roo target JPA2/Hibernate 4. |