runtime exceptions and beans & cascade deletes

[Karthik Guru]

Ques #1

When a runtime exception is allowed to propogate through say the session facade bean layer, the spec says that bean instance will be destroyed.
In weblogic the the remote reference still remains valid.
This is definitely the case with SLSB. I dont know what happens with SFSB.
So I guess weblogic must be configuring the EJBObject with another instance of the bean transparent to us?. Is weblogic still being compliant with spec?

Ques #2

what is the exact bhaviour when we specify <cascade-delete> on relations.
The related beans to which the delete needs to be cacaded need to be loaded in the memory? I mean is it necessary to call ejbRemove() on all the related beans? If that is the case , then guess there is no other alternative but to load the beans.
Can somebody confirm this?

I thought weblogic w'd just issue straight forward delete queries on the related beans using the foreign key.

[Slava Imeshev]

Re: #1

In case of SLSB EJBObject serves as a facade to a pool of SLSB instances. Binding between EJBObject and an instance exists only for duration of a method call. So, yes, next call to a method will/may go to any arbitrary SLSB instance. That's what spec says and that's what weblogic does for you.

In case of SFSB EJBObject is bound to an instance for duration of a session and will become invlaid if runtime exception is thrown.