Bug 914738

Called ejbActive after the create() call on home interface is incorrect by spec.

10.1.3
There are two possible transitions from the pooled to the ready state: through the ejbCreate<METHOD> and ejbPostCreate<METHOD> methods, or through the ejbActivate method. The container invokes the ejbCreate<METHOD> and ejbPostCreate<METHOD> methods when the instance is assigned to an entity object during entity object creation. 
The container invokes the ejbActivate method on an instance when an instance needs to be activated to service an invocation on an existing entity object—this occurs because there is no suitable instance in the ready state to service the client’s call or the ejbTimeout method.

This tescase should be testing the lifecycle callbacks' behaviour.
https://github.com/ochaloup/jboss-as/tree/entitybean-lifecycle-test

It tests the problem of postCreate and activate method. The create and postCreate method should be called in case of moving bean from pooled state to ready when the entity is created by home create method and business method is called. The postCreate should not be called before the business method is called. The activate callback should not be called in this case. The activate method should be called in case that entity bean with the id exists but the entity bean instance is in pool (e.g. after finder method is called).