-
1. Re: JBAS5 integration code for messaging
clebert.suconic May 1, 2007 11:17 AM (in response to anil.saldhana)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. -
2. Re: JBAS5 integration code for messaging
anil.saldhana May 2, 2007 12:51 AM (in response to anil.saldhana)Maybe Scott can comment on this a bit.
-
3. Re: JBAS5 integration code for messaging
timfox May 2, 2007 4:36 AM (in response to anil.saldhana)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. -
4. Re: JBAS5 integration code for messaging
starksm64 May 2, 2007 11:57 AM (in response to anil.saldhana)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, ...).
-
5. Re: JBAS5 integration code for messaging
timfox May 2, 2007 2:27 PM (in response to anil.saldhana)Maybe I'm just not undertstanding what you guys are asking for.