Doesn't make sense then. I would print out the environment from the InitialContext
when you see the NoIntialContextException:
Context iniCtx = null;
try
{
iniCtx = ...
}
catch(NoInitialContextException e)
{
e.printStackTrace();
System.out.println("Env: "+e.getEnvironment());
}
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "jBoss" <[EMAIL PROTECTED]>
Sent: Saturday, December 30, 2000 10:16 AM
Subject: Re: [jBoss-User] NoInitialContextException]
>
> There is no difference between runs. In the first and subsequent runs, the
> client retrieves the initial context like this:
>
> private Context getInitialContext() throws NamingException
> {
> Properties props = new Properties();
>
> props.put(Context.INITIAL_CONTEXT_FACTORY,
>"org.jnp.interfaces.NamingContextFactory");
> props.put(Context.PROVIDER_URL, "cmtexwebdev:1099");
>
> return new InitialContext(props);
> }
>
> The client, however, saves the initial context and then uses it for all the ejb
>calls within each run. Each run, however,
> retrieves its own initial context using the code above.
>
> The client code is identical for each run; so is the ejb code. The only difference
>could be that the first time around, the server
and client code is
> loaded into memory
> and initialized while the second and subsequent times around, cached code might be
>used.
>
> Thank you for your help!
>
> Thomas Kirsch
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
