[Design the new POJO MicroContainer] - Re: Module.getModuleForClassLoader()
by adrian@jboss.org
"kabir.khan(a)jboss.com" wrote :
| "adrian(a)jboss.org" wrote :
| | In fact, I think the first part of your post would be better implemented by listing
| | all existing modules at aop initialization?
| | That way you don't depend upon the specific bootstrap implementation.
| I'm not sure what you mean here? If you mean adding a method returning a map of all loaders and modules, then I think that means AOP will need to come last in the bootstrap? Otherwise as now, it will not pick up the loaders for bootstrap deployments deployed after aop.
|
What is different between that and using the bootstrap if you are asking the question
part way through the bootstrap process?
Maybe a better mechanism would be to use the in/uncallback to be notified of the Modules
as they are constructed/destroyed. That is in fact how they get registered with
the ClassLoading anyway.
from bootstrap/classloader.xml
| <bean name="ClassLoading" class="org.jboss.classloading.spi.dependency.ClassLoading">
| <classloader><null/></classloader>
| <incallback method="addModule" state="Configured"/>
| <uncallback method="removeModule" state="Configured"/>
| </bean>
|
Although you would want them at "Installed" when they are actually usuable
rather than "Configured".
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204704#4204704
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204704
17 years, 2 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: supporting multiple queues.xml
by timfox
"jmesnil" wrote : i've thought a little more about this during the week-end and I'm not sure the feature is worth it.
|
| If our users wants to declare queues spread in many configuration files, they can already do so by having files in separate directories (e.g. a/queues.xml, b/queues.xml,...)
| This is a bit ugly but it works.
|
| If now we want to support multiple queue configuration files from the same directory, things get more complex: we need to scan the directories to find all the matching files (e.g. ending with jbm-queues.xml).
| Either we have to scan all the classpath or allow configuration files only on a specified directory (e.g. config) which must explicitely passed when starting an instance of messaging server. In both case, it is brittle and ugly.
|
| I had a look at JBoss microcontainer deployer to get the functionality but I've not found yet how to provide it in JBM.
|
| Since there is already a solution to support multiple configuration (put them in separate dirs), the only update I'd like to do is to rename the expected file names to jbm-queues.xml to avoid unlikely clash with the more generic queues.xml name.
| If we have some more time before the release of JBM2 GA, I'll revisit this feature but in the mean time, I'll move to more urgent tasks.
|
| wdyt?
|
|
+1
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204676#4204676
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204676
17 years, 2 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: supporting multiple queues.xml
by jmesnil
i've thought a little more about this during the week-end and I'm not sure the feature is worth it.
If our users wants to declare queues spread in many configuration files, they can already do so by having files in separate directories (e.g. a/queues.xml, b/queues.xml,...)
This is a bit ugly but it works.
If now we want to support multiple queue configuration files from the same directory, things get more complex: we need to scan the directories to find all the matching files (e.g. ending with jbm-queues.xml).
Either we have to scan all the classpath or allow configuration files only on a specified directory (e.g. config) which must explicitely passed when starting an instance of messaging server. In both case, it is brittle and ugly.
I had a look at JBoss microcontainer deployer to get the functionality but I've not found yet how to provide it in JBM.
Since there is already a solution to support multiple configuration (put them in separate dirs), the only update I'd like to do is to rename the expected file names to jbm-queues.xml to avoid unlikely clash with the more generic queues.xml name.
If we have some more time before the release of JBM2 GA, I'll revisit this feature but in the mean time, I'll move to more urgent tasks.
wdyt?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204674#4204674
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204674
17 years, 2 months