[jboss-dev] Releasing JBoss 4 with the latest versions of AOP, Remoting, Serialization, etc.

I am summarizing a discussion that has been taking place in private for a while: Messaging relies on the latest versions of AOP, Remoting and Serialization. In oder to make it work in JBoss 4, we need to scope the broker. This is a pain for users: they also need to deploy scoped MDB containers, destination and connection factory MBeans, recovery managers, etc. and from our experience so far, is the fist source of user trouble, as reflected on our user forum. We tried to compensate by writing installation scripts, and detailed documentation explaining the reasons behind this situation and procedures to deal with it, but that doesn't alleviate too much the fact that the whole thing is a pain. All this could be avoided if we start shipping JBoss 4 with the latest releases of Messaging's dependencies (AOP, Remoting and Serialization). If Messaging finds the right versions of the dependency classes it needs in the top-level class repository, the need for scoping disappears. Releases (at least theoretically) are supposed to be backward compatible, so, in theory it should be possible to ship with the latest versions. From discussion with Dimitris , Thomas and Tom Elrod we identified one compatibility problem in Web Services. I am reproducing the discussion below: Thomas Diesler wrote: Tom Elrod wrote: This looks to me like a issue that can be worked out relatively easily. Aside from that, I was wondering if there are other practical consideration that would prevent us to release JBoss 4 with the latest versions of AOP, Remoting and Serialization? Thanks Ovidiu