[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2143) Hotdeployed components can't be configured through components.xml
6:29 a.m.
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 = { 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
4:58 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-2143) Hotdeployed components can't be configured through components.xml
[ 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 = { 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
6:01 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2143) Hotdeployed components can't be configured through components.xml
[ 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 = { 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
5:01 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2143) Hotdeployed components can't be configured through components.xml
[ http://jira.jboss.com/jira/browse/JBSEAM-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 = { 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
5:08 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2143) Hotdeployed components can't be configured through components.xml
[ http://jira.jboss.com/jira/browse/JBSEAM-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 = { 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
7:31 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2143) Hotdeployed components can't be configured through components.xml
[ http://jira.jboss.com/jira/browse/JBSEAM-2143?page=all ]
Pete Muir updated JBSEAM-2143:
------------------------------
Fix Version/s: 2.1.0.GA
(was: 2.0.2.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.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
5:01 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2143) Hotdeployed components can't be configured through components.xml
[ http://jira.jboss.com/jira/browse/JBSEAM-2143?page=all ]
Pete Muir updated JBSEAM-2143:
------------------------------
Component/s: Hot Deploy
(was: Core)
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 = { 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
1 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2143) Hotdeployed components can't be configured through components.xml
[ 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 = { 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
4:47 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2143) Hotdeployed components can't be configured through components.xml
[ http://jira.jboss.com/jira/browse/JBSEAM-2143?page=all ]
Pete Muir updated JBSEAM-2143:
------------------------------
Assignee: (was: 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: 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
9:50 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2143) Hotdeployed components can't be configured through components.xml
[ 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
6:28 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2143) Hotdeployed components can't be configured through components.xml
[ http://jira.jboss.com/jira/browse/JBSEAM-2143?page=all ]
Pete Muir updated JBSEAM-2143:
------------------------------
Fix Version/s: 2.1.0.GA
(was: 2.1.0.BETA1)
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
3:25 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2143) Hotdeployed components can't be configured through components.xml
[ http://jira.jboss.com/jira/browse/JBSEAM-2143?page=comments#action_12412797 ]
Dan Allen commented on JBSEAM-2143:
-----------------------------------
I want to clarify that there is a distinction between "configuring" and
"defining" a component. It *is* possible to configure (the properties of) a hot
deployable component in components.xml. You just cannot define a component this way. As
Pete was saying, if we did allow components to be defined in components.xml, it would need
to be a separate components.xml that resides on the hot deployable classpath (not a bad
idea actually).
If you have a hot deployable component defined as follows:
@Name("myComponent")
public class MyComponent {
private String propA;
// getters and setters as needed
}
You can configure the initial value of the property named propA in components.xml using
the following declaration:
<component name="myComponent">
<property name="propA">initial value</property>
</component>
What you cannot do is the following:
<component name="myComponent" class="MyComponent">
<property name="propA">initial value</property>
</component>
The second XML stanza is a component definition (it has both name and class) and Seam
cannot *see* into the hot deployment classloader in order to fulfill it.
Detailed coverage of this topic can be found in chapters 4 and 5 of Seam in Action.
Hotdeployed components can't be configured through
components.xml
-----------------------------------------------------------------
Key: JBSEAM-2143
URL: http://jira.jboss.com/jira/browse/JBSEAM-2143
Project: 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
5:28 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2143) Hotdeployed components can't be configured through components.xml
[ http://jira.jboss.com/jira/browse/JBSEAM-2143?page=all ]
Pete Muir updated JBSEAM-2143:
------------------------------
Fix Version/s: 2.1.0.BETA2
(was: 2.1.0.GA)
Hotdeployed components can't be configured through
components.xml
-----------------------------------------------------------------
Key: JBSEAM-2143
URL: http://jira.jboss.com/jira/browse/JBSEAM-2143
Project: Seam
Issue Type: Feature Request
Components: Hot Deploy
Affects Versions: 2.0.0.CR2
Reporter: Pete Muir
Priority: Critical
Fix For: 2.1.0.BETA2
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
5893
days inactive
6098
days old
12 comments
4 participants
participants (4)
-
Dan Allen (JIRA) -
Joshua Partogi (JIRA)
-
Norman Richards (JIRA)
-
Pete Muir (JIRA)