[jboss-jira] [JBoss JIRA] Closed: (JBAS-6042) Remove the user of LoaderRepositoryConfig as an attachment

[Adrian Brock (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrian Brock closed JBAS-6042.
------------------------------

    Resolution: Done


This has been done, the configuration change is that the
"Isolated" flag for ears has moved to the EARClassLoaderDeployer further down
the ear-deployers-jboss-beans.xml file.

> Remove the user of LoaderRepositoryConfig as an attachment
> ----------------------------------------------------------
>
>                 Key: JBAS-6042
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6042
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: ClassLoading, Deployers
>            Reporter: Adrian Brock
>            Assignee: Adrian Brock
>             Fix For: JBossAS-5.0.0.GA
>
>
> The 
> ManagedConnectionFactoryClassLoaderDeployer
> JBossEjbParsingDeployer
> JBossAppParsingDeployer
> SARDeployer
> are all creating LoaderRepositoryConfig attachments.
> This currently requires the HackClassLoaderDeployer to convert this into ClassLoadingMetaData.
> This deployers need fixing to generate ClassLoadingMetaData directly
> and this code should not be in the parsing deployers, it applies if the metadata is passed in
> in the predetermined attachments when we don't parse the xml.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira