The EJB 2.0 specification and Ed Roman's book both are silent on the case of a client calling create(...) on the home interface of a stateful session bean at such a time when the limit of the maximum number of Bean instances has already reached. The state diagram has missed the case both in the book and the specification? Have I missed it somewhere :-)?
- Posted by: Vishwesh Singh
- Posted on: August 18 2003 15:09 EDT
It is implementation dependent. The container could either:
- block the call until a bean becomes available
- passivate an idle bean
- ignore the maximum setting altogether and create a new instance