Actually implementing this, there is no need for a Colocation object.
This object already exists in the form of org.jboss.system.Registry
(it should needs adding to the client jar where it will be empty on a client).
Also, looking at org.jboss.proxy.ejb.ProxyFactory
This looks wrong. It creates
If there is going to be a check for an entry in the collocation map, then
effectively the GUID becomes irrelevant. Other cleanup than could be done is
removal of the unused remoteInvoker instance variable.
View the original post :
Only if the non HA invoker deployment also maintained the colocation info.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3859108#3859108
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859108
Ok, I thought you were indicating that the base InvokerInterceptor was going to
be checking for existence in the collocation map which would require the non-ha
proxy factories to maintain this info. Its a less intrusive change if the GUID
continues to be a marker for non-ha collocation and only
