[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-6716) envers should set the TCCL to the envers classloader before constructing a dom4j instance. This will allow applications to use their own version of dom4j
Scott Marlow (JIRA)
noreply at atlassian.com
Fri Oct 7 11:59:19 EDT 2011
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43968#comment-43968 ]
Scott Marlow commented on HHH-6716:
-----------------------------------
We might want to change this in Hibernate also. See http://community.jboss.org/message/630639#630639
> envers should set the TCCL to the envers classloader before constructing a dom4j instance. This will allow applications to use their own version of dom4j
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HHH-6716
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6716
> Project: Hibernate Core
> Issue Type: Improvement
> Components: envers
> Reporter: Scott Marlow
> Fix For: 4.0.0.next
>
>
> forum link http://community.jboss.org/message/630480
> Envers set TCCL to be envers's module classloader before constructing a dom4j instance. This will allow applications to use their own version.
> Also see http://community.jboss.org/wiki/ModuleCompatibleClassloadingGuide section on "How to use JAXP and other service provider APIs from AS/Framework code".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list