> It looks like the orion team just came back. They tend to
> shut down communication during winter, and show up with a new
> release at spring. So I decided to play around with new
> release 2.0 and its classloaders. Orion seems to behave as
> expected, even with shared libraries and shared ej
> Ok. I see what your are talking about. The problem is, Magnus
> does not respond anymore (probably got too rich after the
> oracle deal ;). So it would be good to make sure orion does
> use different classloaders to load the common jar resources
> you are referring to. From what you are descri
> Hmm.
> What do you mean by "share a common classpath"? They all refer to the same
> jar within an EAR? Or you added the class to the system classpath?
In our system we don't pack each application to EARs, we leave them unpacked. Each
application.xml refers to the same classpath, -a path to
bug breaking the
isolation between applications. One can argue if
using static variables is orthodox, but I see no reason why to break the native
classloader hierarchy
Regards
/David Ekholm,
System architect, Net Entertainment AB
Sidenote: We are using the latest version of AXIS and
Orionserver as J2EE platform, essencially the same platform as Oracle
9i.
