[jboss-jira] [JBoss JIRA] (JBAS-7210) JBossContextConfig needs to be isolated from the war class loader
Bruno HALEBLIAN (JIRA)
jira-events at lists.jboss.org
Tue Apr 2 06:56:47 EDT 2013
[ https://issues.jboss.org/browse/JBAS-7210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764327#comment-12764327 ]
Bruno HALEBLIAN commented on JBAS-7210:
---------------------------------------
These 2 referenced patches failed to apply "as is" on JB 5.1.0_GA sources. Line numbers and former $Id tags didn't match because the diffs comply with JB 6.X code source. So I had to adapt the diffs (change line numbers and former $Id tag comment) to have the patch successfully apply on JB 5.1.0_GA sources. That's what I call backport.
I just posted this comment as a HowTo for those who, like me, wanted to hotfix the issue on old running JB5.1 systems with no time for a full JB7 migration.
I fully agree with Brad Maxwell : Upgrading to JB7 is the recommended option, although driving the change from JB5 to JB7 on production systems varies from simple to head-aching (depending on what's deployed)...
> JBossContextConfig needs to be isolated from the war class loader
> -----------------------------------------------------------------
>
> Key: JBAS-7210
> URL: https://issues.jboss.org/browse/JBAS-7210
> Project: Application Server 3 4 5 and 6
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ClassLoading, Web (Tomcat) service
> Affects Versions: JBossAS-5.1.0.GA
> Reporter: Scott Stark
> Assignee: Scott Stark
> Fix For: 6.0.0.M2
>
> Attachments: jbas-7210.war.zip
>
>
> The parsing of the context.xml by the JBossContextConfig class is using the tccl which causes problems when the war app has tried to load its own xml parser.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list