We are in the process of migrating to Spring from EJBs. Our first step is to be able to use Spring to get access to our existing EJBs. It looks to me like SimpleRemoteStatelessSessionProxyFactoryBean is the only option directly provided by Spring, and I have a few concerns about using it at this point in our conversion. We really want to take this slowly, and not make "whole hog" changes that require a lot more regression testing.
1) Looking through the code and documentation, it appears that the proxy it returns is effectively a singlton, and there is no way to change it. I believe that the FactoryBean *has* to be a proxy, since it holds the proxy object, all client objects will share this object. Now, presumably, under the covers, there is an EJB proxy that is provided by my specific EJB provider client library. Won't this be a problem if this is *not* re-entrant? Is it part of the EJB spec that it be re-entrant?
2) Spring offers a great benefit, encapsulating the RemoteException nightmare that Sun foisted on us. However, we're reluctant to change the behavior expected by our current client code all at once. Is there some way to regulate this feature?