[Springframework-developer] EJB access improvements

[<jue...@we...>]

Colin, Rod,

Regarding the following two issues:

http://opensource.atlassian.com/projects/spring/browse/SPR-117

Actually, the contract for Stateless Session Beans is quite odd in that =
respect: You don't really "create" a SLSB with a "create" call, and =
"remove" won't actually remove an instance - as SLSBs are pooled.=20

However, we can easily invoke "remove" on the EJB proxy after the method =
call, both in SimpleRemoteSlsbInvokerInterceptor and in =
LocalSlsbInvokerInterceptor. It seems that this can happen in any case: =
A typical container will simply ignore the "remove" call anyway.

http://opensource.atlassian.com/projects/spring/browse/SPR-129

I've just added a "cacheHome" flag to AbstractSlsbInvokerInterceptor. If =
turned off, the home object will be refetched on each method invocation. =
This is intended for development environments: It allows for hot =
redeploy of the target EJB respectively restart of the EJB container.


I've just added the corresponding code, as it shouldn't change anything =
in typical cases. I'll commit it by tomorrow morning. If you object to =
either of these changes, we can still roll them back before 1.0.2.

For addressing the second issue, there are a couple of further options =
mentioned in the JIRA entry: for example, refetching the home object =
when the create invocation fails. However, those are probably beyond =
1.0.2.

Juergen