On May 27, 2005, at 6:25 PM, Tor-Einar Jarnbjo wrote:
Geir Magnusson Jr. wrote:
(Tomcat : I'd bet they fixed that (or will fix...))
It doesn't seem so. The SSL code has been in Tomcat versions 4.1.x
to 5.5.9 and I just saw that also the LDAP code in Tomcat 5.5.9
uses classes in com.sun.
Amazing. Jetty was doing the same thing until we asked them to fix
it. They did, and all is well now.
Well, can't the VM just prevent non-kernel code from using them?
Maybe overhead too high?
How do you distinguish "kernel code" and "non-kernel code"? From
the VM point of view, the classes in the java(x).* packages do not
differ from user code classes and it is also possible to bootstrap
the VM and replace java(x).* classes with own implementations. Been
there, done that.
I meant execution context. Is there a clear boundary between code
thats executing in the context of the VM and code that's executing in
the context of the 'user' app?
geir
--
Geir Magnusson Jr +1-203-665-6437
[EMAIL PROTECTED]
