> 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
On 3/20/03 02:36 PM David Ekholm <[EMAIL PROTECTED]> wrote:
> Thank you for taking time trying to resolve this. I totally agree that
> the Orion team are probably too rich by now. We haven't got any answers
> from them for a long time either :-/
It looks like the orion team just came back. They
> 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
