This content has been marked as final.
Show 3 replies
-
1. Re: Simplifying the JBM beans deployment
jmesnil Apr 8, 2009 7:25 AM (in response to timfox)there are 4 beans which may still need to be injectable from the configuration file:
- JBMSecurityManager
- MBeanServer
- JNDIServer
- Naming
We have our own implementations when running in standalone but these beans will have to change their implementation when we run JBM in JBoss AS 5 (i'm not sure that'll be the case for the 2 jndi pojos but they also define properties in the configuration file)
All the others are implementation specific and do not really need to be exposed from the conf. -
2. Re: Simplifying the JBM beans deployment
timfox Apr 8, 2009 7:28 AM (in response to timfox)JNDIServer is completely independent so shouldn't need to be injected anywhere.
What's Naming? Can't see it in jbm-standalone-beans.xml
JBMSecurityManager, yes, this can remain injectable
MBeanServer yes also. -
3. Re: Simplifying the JBM beans deployment
jmesnil Apr 8, 2009 7:35 AM (in response to timfox)"timfox" wrote:
JNDIServer is completely independent so shouldn't need to be injected anywhere.
What's Naming? Can't see it in jbm-standalone-beans.xml
Naming is the 1st bean defined in jbm-standalone-beans.xml
As you said, both jndi beans are already independent.
So it leaves only 2 beans to be injectable:
- JBMSecurityManager
- MBeanServer