[jboss-jira] [JBoss JIRA] Resolved: (JBAS-5892) ClientLauncher relies on full metadata to obtain classpath

[Scott M Stark (JIRA)]

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

Scott M Stark resolved JBAS-5892.
---------------------------------

    Resolution: Done


The JBossClientMetaData is not accessed until the ClientContainer is being created with the app client mc class loader using a jndi value dependency.


> ClientLauncher relies on full metadata to obtain classpath
> ----------------------------------------------------------
>
>                 Key: JBAS-5892
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5892
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: AppClient, Deployers
>            Reporter: Scott M Stark
>            Assignee: Scott M Stark
>             Fix For: JBossAS-5.0.0.CR2
>
>
> There is a circularity problem with how the app client launcher obtains the client classpath by downloading the JBossClientMetaData from the server. This can include deployment specific interfaces that require the client classpath to load. The classpath information needs to be made available separately from the JBossClientMetaData and a class loader created before loading the JBossClientMetaData.

-- 
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