"bill.burke(a)jboss.com" wrote : don't see the reason for the extra
complication
Read the other threads! Why do we need to repeat everything already discussed
every time you post?
e.g. One advantage is being able to summarize duplicate names of beans in
different deployments in the IncompleteDeploymentException.
Currently you get an exception but it is not included in the summary because
you can't install two beans with the same name. So all knowledge of the
duplicate context is lost.
Another is that is not more complicated, it is less.
The MC deals with a single id (guaranteed unique) rather leaving it to the different
contexts (and the user) to control.
Finally, it is required for when we eventually get around to transactional deployment,
where you don't do
| uninstall bean1
| // Bean is unusable for a "long time"
| install bean1
|
you do
| prepare to install GUID2 (name=Bean1)
| prepare to uninstall GUID1 (name=Bean1)
| vote
| handoff state GUID1 -> GUID2 (e.g. socket/jndi front ends and other injections)
| uninstall GUID1
| // Almost nothing since the handoff already changed which is the active one
| install GUID2
|
i..e. There are two beans being managed with the same name, but only one is the
"active" one.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039253#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...