[jboss-dev] JBoss Messaging - to scope or not to scope

[Tim Fox]

There have been several critical fixes in remoting since 2.0.0 that 
without which neither JBM nor JBoss ESB will work (if using JBM as 
transport)

This means that if AS 4.2.0 uses remoting 2.0.0 then JBoss ESB would 
also have to be deployed scoped to use remoting 2.2.0. :(

I believe this is only the case if ESB is using JBM as it's transport. 
But JBM is supposed to be the default transport in JBoss ESB.

I think we really need to push to get AS 4.2.1 to use remoting 2.2.0 
ASAP otherwise this is going to be a useability nightmare not just for 
JBM but for JBossESB too.

Anyone else got any more ideas how we can work around this?



Dimitris Andreadis wrote:
> +1
> 
> Adrian wrote:
>> In summary:
>>
>> It's almost certainly too late to discuss retesting now.
>> You'd have to get at least Dimitris, QA, the EJB3 and webservices
>> teams to agree to redo all their testing.
>>
>> You want to look instead at getting a patched remoting 2.0.x (or 2.2.0
>> if it is compatible) in JBoss-4.2.1 when they will have to retest
>> anyway.
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development