On the project I'm working on, we've got a situation where it would extremely valuable to be able to have parameterized ejbCreate() methods on our stateless session beans, but the spec doesn't allow for this (we could put them in, but they'd never get invoked).
One alternative would be to use stateful session beans, which allow this type of functionality. The client would still be using the session bean in a stateless manner, however, e.g. one method call and it's done. Is anyone aware of the potential overhead implications of making all of the session beans stateful versus stateless? If it matters, the beans would be deployed under WL 6.1.
The other alternative that we're currently heading down is to take the parameter we'd like to pass in to ejbCreate() and add it to all of the business methods defined in the remote/local interface.
Thoughts?
-tb
***************************************************************************************
WARNING: All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.
***************************************************************************************
