-
1. Re: AOP classloader issues
clebert.suconic Mar 15, 2007 2:34 PM (in response to timfox)I'm testing this right now...
I also had to change where ServerPeer was deploying serverSideAOP...
I have removed all the setTCLs from the code... and because of this messaging-users and roles.properties will have to be placed on the correct location under messaging/conf (not in our scoped sar location any more).
This was working under our sar location because of the hack on setClassLoader. -
2. Re: AOP classloader issues
clebert.suconic Mar 15, 2007 6:11 PM (in response to timfox)So, because of the removal of the TCL I had to do this change:
http://fisheye.jboss.org/browse/Messaging/branches/Branch_1_2_0_SP/util/release-admin.xml?r1=2548&r2=2546
Ovidiu, if you could please double check this... Maybe you would find a better way to do this move/copy. -
3. Re: AOP classloader issues
timfox Mar 15, 2007 6:25 PM (in response to timfox)What I don't understand is why there was a messaging-users.properties/messaging-roles.properties in server/deploy/jboss-messaging.sar at all.
I would say the correct place for security config is in conf -
4. Re: AOP classloader issues
clebert.suconic Mar 15, 2007 6:29 PM (in response to timfox)What I don't understand is why there was a messaging-users.properties/messaging-roles.properties in server/deploy/jboss-messaging.sar at all.
Yes.. the correct place is under /conf...
When we had that hack in place (setting the ThreadContextClassLoader), The security would look for those files in our scoped classLoader.
I'm glad we could get rid of this thing finally.