Actually that is not an API that should be rather termed as SPI. Interestingly, EJB specification 2.0 does not define all the SPIs between container and persistence manager. Current SPIs that are present in EJB specification 2.0 deal with passing lifecycle events to the persistence manager, but otherwise many things depend on the proprietary implementation of EJB container and Persistence Manager provider. If your requirement is more of lifecycle types, you can check chapter 9.0 of EJB specification, since that may help you. For rest of the service contracts between container and persistence manager, I think you will have to work it out with both of them.

This can be considered as one of the ambiguities left in the spec, that should be fixed in the future specifications otherwise the idea of pluggable persistence managers cannot become a reality.

Hope this helps,

Reema.