The SecurityManager issue does appear to be resolved in the JBoss3.2.3/Tomcat4.1.29
bundle.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835438#3835438
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3835438
This issue does appear to be resolved in the JBoss3.2.3/Tomcat4.1.29 bundle.
If anyone knows the precise location of the fix, however, I would be very grateful for
a pointer. It is no trivial matter for my organisation to upgrade our production
systems but I could get an updated JAR past the ad
This issue does appear to be resolved in the JBoss3.2.3/Tomcat4.1.29 bundle.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835436#3835436
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3835436
---
This significant issue has appeared a couple of times in a couple of fora without any
resolution. It is serious in nature so I will restate ...
Where there is a requirement to set a SecurityManager for the JVM (ie. when dynamic
RMI classloading is required), Catalina fails to deploy _any_ WAR fi
I am having _exactly_ the same problem using dynamic class loading in an attempt to
access Jini services.
Curiously, neither of us are attempting to access resources via JNDI so Catalina must
be confused. Is this a bug with JBoss/Tomcat integration?
View the original post :
http://www.jboss
