> > So you're going for BMP then? Or do you want to do this with stateless
> > session beans only?
> > > > By
> > > > wrapping it in a stateless session bean you can "batch" keys.
> > > >
>
> Before I answer this question please let me know - does the entity bean
> looses al it's state when it goes back to the pool and under what
> circumstances the framework decides to get it back in the pool?
The instance is not "reset" when it is put back into the pool (i.e. when it
is passivated). However you should not rely on that kind of state, of
course.
> Why do you think that using a 'singleton' statless bean would 'be
> introducing an unnecessary bottleneck '?
Because if 10 clients try to access it at the same time 9 will have to wait,
since access to the instance have to be serialized (in accordance with the
EJB spec). In your case I think you can use the standard session pool with
many instances, since you do not require the generated keys to be in order.
/Rickard
