As far as fixing Main.java... I won't be able to fix as we have already
locked down our jboss version. :(
The problem is further impacted by the fact that the integration between the
tomcat classloader and jboss classloader seems to be flawed. I have to put
my security classes in $JBOSS_HOME/lib/ext & have to put them in my
classpath.
Also, if I put my login_MBean in the classpath, jboss pukes because it can't
find org.jboss.util.ServiceMBeanSupport. I found that this is located in the
jboss.jar.
Well, if I include jboss.jar in my classpath jboss starts thoughing null
pointers all over the place.
The only solution is to maintain to jar files! One of which has all my
security stuff but my loginMbean and the other with the MBean. I have to put
one jar in the classpath and the other in lib/ext. This is going to be a
nightmare to maintain!
Basically, I think that everything would be ok if tomcat would just find the
classes loaded from lib/ext but this doesn't happen in 2.2.2. What about
3.0?
d.
-----Original Message-----
From: marc fleury [mailto:[EMAIL PROTECTED]]
Sent: Saturday, August 04, 2001 2:46 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] JAAS requires staticly loaded classes?
|I removed the security code from the Main altogether for the 3.0 series. It
|should really be an MBean configured as such. Make sure to move the classes
|after the "contextThread setting". Didn't you learn anything in
|class? well
|at least you come up with real questions :)
Also scott is on a JBG consulting gig next week and preparing for it before
departure so don't expect him to fix it for you, now get moving, use those
fingers
marcf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
