Bug 724371 (BRMS-317) - Two different versions of xml-apis jars included in WEB-INF/lib directory
Summary: Two different versions of xml-apis jars included in WEB-INF/lib directory
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-317
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: unspecified
Version: 5.0.1
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: 5.1.0 GA
Assignee: Jervis Liu
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-21 16:40 UTC by Tihomir Surdilovic
Modified: 2013-11-07 22:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-23 09:38:33 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-317 0 None Closed Two different versions of xml-apis jars included in WEB-INF/lib directory 2012-06-14 14:56:58 UTC

Description Tihomir Surdilovic 2010-05-21 16:40:32 UTC 
securitylevel_name: Public

This affects both 5.0.1 and 5.0.2. in WEB-INF/lib you can find 

xml-apis-2.0.2.jar
xml-apis-2.7.1.jar

If you remove both of these the webapp still deploys and runs fine so I am not really sure of the reason we are shipping these jars.
Comment 1 Jervis Liu 2010-09-15 17:56:48 UTC 
This is not an issue anymore. BRMS 5.1(Drools 5.1 Guvnor ) does not ship xml-apis jars anymore.
Comment 2 Dana Mison 2010-10-27 02:54:43 UTC 
Release Notes Text: Added: test
Comment 3 Dana Mison 2010-10-27 03:13:05 UTC 
Release Notes Text: Removed: test
Comment 4 David Le Sage 2010-11-01 00:42:43 UTC 
Release Notes Docs Status: Added: Documented as Resolved Issue
Writer: Added: dlesage
Release Notes Text: Added: Two different versions of the xml-apis JAR file were included in the WEB-INF/lib directory, causing confusion for users.  As xml-apis is no longer a required component, both of these have been removed.
Note You need to log in before you can comment on or make changes to this bug.