users@glassfish.java.net

Re: Problem with deserialization EJB Handle and getting remote EJBObject

From: <glassfish_at_javadesktop.org>
Date: Tue, 14 Oct 2008 08:49:39 PDT

> ksak, thanks for your reply
>
> Yes, I'd undeployed application before I tried to use
> HomeHandle to retrieve EJBHomeObject and create
> EJBObject. When I try to disable application and
> enable it again - all works fine. Beans are destroyed
> then, aren't they?

I'm not that familiar with that particular admin operation but I believe disabling is not considered undeploying the app. It probably means if you were to restart the appserver that application would not be loaded.

>
> I can't undestand one thing:
> 1. I'm able to deserialize handle
> 2. I'm able to get EJBHome (to which object? )
> 3. I'm able to cast EJBHomeObject to my specific
> class
> 4. I not able to invoke create() method on home
> interface to get instance of bean.
>

It's just an implementation detail that it happens to fail on the fourth step and not earlier.
What is your use-case exactly? The handle functionality was not intended to preserve
bean access after the application is undeployed.


> TIA
> Beniamin
[Message sent by forum member 'ksak' (ksak)]

http://forums.java.net/jive/thread.jspa?messageID=306800