I supose that *transaction demarcation API* is javax.transaction.UserTransaction's methods.
The terms resource-manager udsed in this chapter refer to the ressources declared in the deployment descriptor using the resource-ref element. This includes not only databases resources, but also JMS connections...these resources are considered to be all managed by the container
While an instance is in a transaction, the instance must not attempt to use the resource-manager specific transaction demarcation API i.e must not commit or rollback method on the java.sql.Connection interface or on the javax.jms.Session interface
you shouldn't interfere with the Container's demarcation of transaction boundaries
a SELECT can return either an <abstract-schema-type> (which really means the bean's local component interface type
, so if not done, it must call the ejbLoad method.
The container synchronizes the instance's state before it invokes the ejbRemove method
The local home interface allows a local client to do the following:
- create a new session object
- remove a session object