[jboss-user] [Microcontainer] - Re: Towards remoting-jboss-beans.xml

alesj do-not-reply at jboss.com
Wed Nov 5 10:58:22 EST 2008


"ron.sigal at jboss.com" wrote : 
  | 1. Are there any hidden gotcha's I'm missing?
  | 
Dunno.
You tell me, when you hit them. ;-)

"ron.sigal at jboss.com" wrote : 
  | 2. Are there any conventions, e.g. naming conventions, I should be aware of?
  | 
Not that I'm aware of.
Perhaps keeping old MBeans, that are now plain POJOs,
still in the MBean server with the help of @JMX.

"ron.sigal at jboss.com" wrote : 
  | 3. Am I correct in understanding that setting "registerDirectly=false" in org.jboss.aop.microcontainer.aspects.jmx.JMX supports hot deployment?
  | 
Dunno, check ServiceControllerRegistrationLifecycleCallback for more details. It's a JMX issue / question.

"ron.sigal at jboss.com" wrote : 
  | 4. JBAS-3926 is "Move remoting transports out of conf/jboss-service.xml to a remoting-beans.xml", but I see that all the *-beans.xml files in AS 5 are named *-jboss-beans.xml.  Is the latter form just a convention for *-beans.xml files that come with the AS?
  | 
Yes, they were renamed to be more JBoss specific.
Since we do file --> metadata matching mostly based on suffix,
we would also pick some Spring -beans.xml named files,
which were only meant to be used by strict Spring core lib.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187017#4187017

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187017



More information about the jboss-user mailing list