[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2143) Hotdeployed components can't be configured through components.xml

Pete Muir (JIRA) jira-events at lists.jboss.org
Fri Mar 14 10:50:28 EDT 2008

     [ http://jira.jboss.com/jira/browse/JBSEAM-2143?page=all ]

Pete Muir updated JBSEAM-2143:

    Issue Type: Feature Request  (was: Bug)

> Hotdeployed components can't be configured through components.xml
> -----------------------------------------------------------------
>                 Key: JBSEAM-2143
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2143
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Hot Deploy
>    Affects Versions: 2.0.0.CR2
>            Reporter: Pete Muir
>            Priority: Critical
>             Fix For: 2.1.0.GA
> he hot deployment scanner is isolated, using a URLClassloader that is not available once that method comes to a close. The only way to make this work would be to keep that classloader alive during the rest of the startup process. I can direct you to the line of code that you need to look at if you are curious about it.
> Check out lines 540 and 541 or org.jboss.seam.init.Initialiation. The scanForHotDeployableComponents uses the following logic to create a component scanner:
>             URL[] urls = { url };
>             classLoader = new URLClassLoader(urls, Thread.currentThread().getContextClassLoader());
>             paths = new File[] { directory };
> Once it processes the classes, that classloader is discarded and obviously, since it is a URLclassloader, the classes aren't going to be found later on. 

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


More information about the seam-issues mailing list