Created: (JBSEAM-2143) Hotdeployed components can't be configured t

Thread: Created: (JBSEAM-2143) Hotdeployed components can't be configured t

Search this list only Search all lists
Created: (JBSEAM-2143) Hotdeployed components can't be configured t
	2007-10-23 06:29:03
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: Bug Components: Core Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Priority: Critical Fix For: 2.0.1.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 = ; classLoader = new URLClassLoader(urls, Thread.currentThread().getContextClassLoader()); paths = new File[] ; 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.atl assian.com/software/jira _______________________________________________ jbossseam-issues mailing list jbossseam-issueslists.jboss.org https://lists.jboss.org/mailman/listinfo/jbossseam-issu es

Assigned: (JBSEAM-2143) Hotdeployed components can't be configured
	2007-11-23 16:58:18
[ http://jira.jboss.com/jira/browse/JBSEAM-2143?page=all ] Pete Muir reassigned JBSEAM-2143: --------------------------------- Assignee: Pete Muir > 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: Bug > Components: Core > Affects Versions: 2.0.0.CR2 > Reporter: Pete Muir > Assigned To: Pete Muir > Priority: Critical > Fix For: 2.0.1.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 = ; > classLoader = new URLClassLoader(urls, Thread.currentThread().getContextClassLoader()); > paths = new File[] ; > 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.atl assian.com/software/jira _______________________________________________ jbossseam-issues mailing list jbossseam-issueslists.jboss.org https://lists.jboss.org/mailman/listinfo/jbossseam-issu es

Updated: (JBSEAM-2143) Hotdeployed components can't be configured t
	2007-11-30 06:01:46
[ http://jira.jboss.com/jira/browse/JBSEAM-2143?page=all ] Pete Muir updated JBSEAM-2143: ------------------------------ Fix Version/s: 2.0.2.GA (was: 2.0.1.GA) > 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: Bug > Components: Core > Affects Versions: 2.0.0.CR2 > Reporter: Pete Muir > Assigned To: Pete Muir > Priority: Critical > Fix For: 2.0.2.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 = ; > classLoader = new URLClassLoader(urls, Thread.currentThread().getContextClassLoader()); > paths = new File[] ; > 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.atl assian.com/software/jira _______________________________________________ jbossseam-issues mailing list jbossseam-issueslists.jboss.org https://lists.jboss.org/mailman/listinfo/jbossseam-issu es

Commented: (JBSEAM-2143) Hotdeployed components can't be configured
	2008-01-05 05:01:43
[ http://jira.jboss.com/jira/browse/JBS EAM-2143?page=comments#action_12393911 ] Joshua Partogi commented on JBSEAM-2143: ---------------------------------------- Does this mean that in the future release components that is configured through components.xml will be able to be hot deployed? > 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: Bug > Components: Core > Affects Versions: 2.0.0.CR2 > Reporter: Pete Muir > Assigned To: Pete Muir > Priority: Critical > Fix For: 2.0.2.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 = ; > classLoader = new URLClassLoader(urls, Thread.currentThread().getContextClassLoader()); > paths = new File[] ; > 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.atl assian.com/software/jira _______________________________________________ jbossseam-issues mailing list jbossseam-issueslists.jboss.org https://lists.jboss.org/mailman/listinfo/jbossseam-issu es

Commented: (JBSEAM-2143) Hotdeployed components can't be configured
	2008-01-05 05:08:53
[ http://jira.jboss.com/jira/browse/JBS EAM-2143?page=comments#action_12393913 ] Pete Muir commented on JBSEAM-2143: ----------------------------------- In some form, yes. Possibly you will need a separate components.xml that is hot deployable > 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: Bug > Components: Core > Affects Versions: 2.0.0.CR2 > Reporter: Pete Muir > Assigned To: Pete Muir > Priority: Critical > Fix For: 2.0.2.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 = ; > classLoader = new URLClassLoader(urls, Thread.currentThread().getContextClassLoader()); > paths = new File[] ; > 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.atl assian.com/software/jira _______________________________________________ jbossseam-issues mailing list jbossseam-issueslists.jboss.org https://lists.jboss.org/mailman/listinfo/jbossseam-issu es

Updated: (JBSEAM-2143) Hotdeployed components can't be configured t
	2008-02-11 13:00:33
[ http://jira.jboss.com/jira/browse/JBSEAM-2143?page=all ] Norman Richards updated JBSEAM-2143: ------------------------------------ Fix Version/s: 2.1.0.GA (was: 2.1.0.A1) > 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: Bug > Components: Hot Deploy > Affects Versions: 2.0.0.CR2 > Reporter: Pete Muir > Assigned To: 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 = ; > classLoader = new URLClassLoader(urls, Thread.currentThread().getContextClassLoader()); > paths = new File[] ; > 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.atl assian.com/software/jira _______________________________________________ jbossseam-issues mailing list jbossseam-issueslists.jboss.org https://lists.jboss.org/mailman/listinfo/jbossseam-issu es

[1-6]

about | contact Other archives ( Real Estate discussion Medical topics )