Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 899869 (JBPAPP6-1626)

Summary: org.w3c.dom.html.HTMLDOMImplementation present in jython-standalone-2.5.2-redhat-1.jar and xercesImpl-2.9.1-redhat-1.jar
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Rostislav Svoboda <rsvoboda>
Component: unspecifiedAssignee: David Walluck <dwalluck>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: dwalluck, jjaggars, miclark, pgier
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBPAPP6-1626
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-04 19:06:17 UTC Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 900190    

Comment 1 Paul Gier 2012-04-02 21:34:54 UTC
This class is also present in both upstream jars.  I'll leave it up to Fernando whether we should fix this in our builds.

Comment 2 Shelly McGowan 2012-04-05 20:00:17 UTC
@David, can you comment on this.

Comment 3 David Walluck 2012-04-05 20:31:04 UTC
The jython-standalone jar is, by upstream design, a monolithic jar containing many third-party libraries, only a few of which are package-renamed. Right now, several issues have been opened by QA that are all due to this one fact so I do not think anything is gained by listing each and every jar that is duplicated (or at least they should be opened as sub issues to one main issue).

I would like to find out from the upstream jboss dev who depends on jython specifically what they are using so that we can remove or stop using the bundled third-party jars. However, another issue is that the non-standalone jar (jython.jar) does not exist on maven central for the latest version, so it's not possible to try in the community. I think that maybe an upstream jython bug should be filed about that.

Also, the jython-standalone jar contains the .py libraries, whereas the jython jar contains only the Java implementation, but no copy of the standard python libraries. If I were the upstream jython project, I would have put the python libraries in a separate jar altogether.


Comment 4 Mike Clark 2012-04-08 17:00:48 UTC
Hey folks,

The jython-standalone jar provides a java jython interpreter used by the JDR system to generate diagnostic information for GSS.  The third party jars are included as part of the interpreter implementation.  I do not think it is wise to pick it apart unless we are seeing some conflict with the other versions delivered in EAP.    The as7 modular classloading should prevent any problems.  Note that it is a private module.

(Of course, if there an actual conflict with any of the classes in jython-standalone.jar, we'll need to address it.)

Comment 5 David Walluck 2012-04-11 17:33:26 UTC
Parent: Added: JBPAPP-8684


Comment 6 David Walluck 2012-04-18 23:23:34 UTC
The current plan is to update the module.xml so that it uses xerces:xercesImpl that is shipped with EAP and remove the classes from the jython-standlone jar.

Comment 7 Paul Gier 2012-05-04 19:02:28 UTC
Link: Added: This issue duplicates JBPAPP-8928


Comment 8 Paul Gier 2012-05-04 19:05:21 UTC
Link: Removed: This issue duplicates JBPAPP-8928 


Comment 9 Paul Gier 2012-05-04 19:06:17 UTC
This will be fixed as part of JBPAPP-8684

Comment 10 Fernando Nasser 2012-11-13 23:12:51 UTC
Docs QE Status: Removed: NEW