Hi Niclas,
Works perfectly! Thanks a lot! Now I've understood the classloader
chain clearly. Once again, thanks a lot for your help.
Brgds,
R. Saravanan
On Wed, 22 Sep 2004 03:39:24 +0800, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
> On Wednesday 22 September 2004 03:28, Niclas Hedhman wrote:
>
On Wednesday 22 September 2004 03:28, Niclas Hedhman wrote:
> Let me think a few minutes.
Without re-organizing your app, you might be able to do;
ClassLoader cl = getClass().getClassLoader();
Thread.currentThread().setContextClassLoader( cl );
in the Panel class just before you lookup the Home
On Wednesday 22 September 2004 01:29, Rajamani Saravanan wrote:
> Hope I'm getting the point across??
Yes you do.
I kind of understand the problem;
The Panel class tries to get an instance to the Home interface and therefor do
a lookup via JNDI, which is initialized in the Main container. When
Hi Niclas,
> Before trying to un-nest this situation I have a few questions;
>
> 1. "I have a main block which establishes a connection to a J2EE server", does
> that mean you are running Merlin outside the J2EE container or you have
> Merlin inside the J2EE container? If inside, then which cont
Before trying to un-nest this situation I have a few questions;
1. "I have a main block which establishes a connection to a J2EE server", does
that mean you are running Merlin outside the J2EE container or you have
Merlin inside the J2EE container? If inside, then which container are we
talki