Peter, Stefano,

Yes and no. There is so many broken APIs such as this and more keep coming out each day. For instance JNDI is a JVM wide setting, JDK1.4 logging is JVM wide, JDK 1.4 Prefs is JVM wide etc. This is not even to mention the Policy objects and half the security API. More and more of the JVM is being forced into the "single JVM, single app" model which completely bites.

That's well put. Even things like XML parsing suck. IoC should rule for all provided services.

Other real options include * moving SarURLStreamHandler to system classloader and going with ugly tight coupling.

-1

* extracting jars into tmp/work directory and reusing them (like how Pauls sugested using MetaJarToolkit)

I thought it did not unpack. I thought it managed it all inside the jar by virtue of a hook class.

* writing our own ClassLoader

+1

* ignoring this factor and always extracting lib

For Interim +1

* something else?

-0

- Paul H



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>



Reply via email to