yeah, that's better. i didn't know about that approach.
something to think about, however, is that the security manager may
break clients in unexpected ways. it will most likely just result in
some exception stack trace being printed somewhere, but the exit() call
may be invoked from within code that has an exception handler that tries
to do something meaningful and (unbeknownst to the author of the code)
in this case destructive. using the "hack the JVM classes" route would
result in System.exit() becoming a no-op. This could either work (the
thread unwinds cleanly) or fail grossly,
truthfully, no matter what you do, if you write code that prevents the
exit, you may get some weird behavior.
-rg
(by the way, i dont know if recompiling JVM classes works, or is even
legal!)
> -----Original Message-----
> From: Aaron Mulder [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 08, 2000 1:55 PM
> To: jBoss
> Subject: RE: [jBoss-User] Protection from System.exit(0);
>
>
> Ewww! Recompiling JVM classes? Let's not go there! How about
> using a security manager instead.
>
> Aaron
>
> On Fri, 8 Dec 2000, Rhett Guthrie wrote:
> > not sure if this will work, but you could modify
> java.lang.System.java
> > rebuild java.* packages from the src.jar that comes with
> the JDK. re-jar
> > rt.jar (the packages are sealed so they need to be
> together.) run your
> > app server on your hacked JDK.
> >
> > i would try it, but i dont know if it will work. i think the vm does
> > some weird stuff that breaks when you try this. i once
> tried to rebuild
> > javax.naming (so i could get some debug info for JBuilder).
> JBuilder, at
> > least, didn't like it...
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
