JBAS5 integration code for messaging

[anil.saldhana]

I am making changes to the security layer. All layers that integrate into JBoss Application Server5 will be affected if there is direct usage of SecurityAssociation and such. Messaging is one of the affected components.

Is it possible for you to move the JBAS5 integration code base from messaging project into the JBAS trunk? I am particularly pointing towards org.jboss.jms.xxxx :)

I think the integration code for AS4.2, 5.0 should be in the workspaces of JBAS.

[clebert.suconic]

We have SecurityAspect using SecurityAssociation, which has to be part of our codebase. We would need to do some refactoring to have the security integration code moved to JBAS/trunk.

Also, we will have to take in consideration that the same version of Messaging will also run on JBAS 4.0.. so we will need some integration code at our side for JBAS 4.0.

[anil.saldhana]

Maybe Scott can comment on this a bit.

[timfox]

We need this code both when we're running standalone and in the AS.

I suggest the best thing to do here is to separate it the security code into its own jar, then the AS can depend on that, and we can then depend on that.

This means we don't have to depend on the whole AS and the code is in one place.

[starksm64]

We need a stable security spi and aspects that use that in the security projects, and then environment integration pieces that inject the environment specific implementation of the security spi so that projects only depend on the stable security spi/aspects. The environment specific implementation has to live in the associated projects (jbossas, esb, ...).

[timfox]

Maybe I'm just not undertstanding what you guys are asking for.