Problem with Application context when deploy two ear (based on seam).

[vtyro]

Please, help...
I put two ear based on JBSeam in jboss deploy. In first ear stateful session bean method is invoked from JNDI (remote inteface) for authentificate.

/// Code from ear1

if(service == null) {
    InitialContext context = JNDIContextService.getContext("service-jndi.properties");
    service = (IRmiService)context.lookup("service/RmiService/remote");
    saleTicketService.login("login", "passwd");
}

///

In other ea in session bean do next:

/// Statefull from ear2

Lifecycle.mockApplication();
Lifecycle.beginCall();
Lifecycle.beginSession(new Hashtable<String, Object>());
Identity.instance().setUsername(username);
Identity.instance().setPassword(password);
Lifecycle.mockApplication();
Identity.instance().login();
Lifecycle.endCall();

///

But Identity.instance().login(); doesn't work correctly. I have traced code and searched, that the Application context was changed during invoke Identity.instance().login() and it became same as context from first ea when execute EL authenticate-method #{Authenticator.authenticate}!?

If i use two different jboss servers for ears, it works correctly...

[pmuir]

Why are you mocking the application like that? Assuming your service is a Seam component there is no need.

Anyway, I guess it depends on whether the same thread is used on the server side of the rpc call. (I guess it is, but I don't know much about EJB3, I think you should be able to alter this).

[vtyro]

Thanks.

Why are you mocking the application like that?

Yes. Instead web-service I use rmi.

I guess it depends on whether the same thread is used on the server side of the rpc call.

It's correct, where it thread overlap.
In session bean has its Application context, but I guess during Identity.login invoke native methods, in which the thread switch.