"adrian(a)jboss.org" wrote : "scott.stark(a)jboss.org" wrote :
| | Like I said before. The container project (and the classloader project)
| | shouldn't be in the MC build. They are only there because the MC was initially
| | the major consumer while we developed them.
|
| If/when this is split out, can we have a separate artifacts from container for metadata etc. for JDK 1.4 like we do for JDK 5?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082192#4082192
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082192
To document our chat:
In 4.2 it works like this:
BeanA is the parent of a nested SFSB hierarchy. It holds a ref to the BeanB SBC (and to the XPC). The "one serialized unit" you mention is passivated under BeanA.id.
When BeanB is passivated, what gets written to disk under BeanB.id is a ProxiedStatefulBeanContext; a proxy. If the user activates BeanB, the ProxiedStatefulBeanContext is activated and knows how to find BeanA's cache, find the BeanA SBC in that cache, and find the real BeanB SBC inside the BeanA SBC. The ProxiedStatefulBeanContext then delegates all calls to the real BeanB SBC.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082191#4082191
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082191
"sacha.labourey(a)jboss.com" wrote : "adrian(a)jboss.org" wrote :
| | Why did you release 2.0.0.Beta4 without first a snapshot of the latest stuff in jboss-head?
| | This will have to wait until RC1 now :-(
|
| Should we fix those and re-do a new beta ASAP?
Actually, I don't think the problem is really in aop-mc-int anyway.
The issue is that the default aspect from aop-mc-int registers directly
with the MBeanServer.
But the thing that gets registered implements ServiceMBeanSupport
so it "lazily" registers itself with the ServiceController.
This leads to double unregistration.
Inside the appserver, the advice should be replaced with one that
(un)registers with the ServiceController.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082166#4082166
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082166