How to give #ejbCreate 'Required' transaction semantic

Question

I'm can't get the #ejbCreate method on my BMP Entity to provide the 'Required' transactional semantic. The need is for a client to have a transaction that updates several EJBs and also creates one. But I'm finding that if the transaction rollsback the #ejbCreate is still persisted.
I have defined 'create' mewthod to be 'Required' in the container-transaction element of the deployment descriptor but this has not helped. Ie
<container-transaction>
<method>
<ejb-name>Order</ejb-name>
<method-name>create</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
The updates are clearly not affected because they are only persisted when #store is called which only happens if the transaction commits. But all the examples I have ever seen actually inserts DB records during #ejbCreate, and this seems to be happening in its own transaction - though I don't know why and haven't been able to actually confirm that in any case.
I'd really like to know how to declaratively define the appropriate transaction semantic, but failing that I was wondering if anyone knew whether it is safe to move the persistence for #ejbCreate into #store and just have #ejbCreate determine the PK?

Answer 1

Its definitely the create that I want to define as having the "Required" semantic.
It doesn't seem to matter where I call it from (a SSB method with Required transaction or Struts Action that explicitly demarcates transaction), the #ejbCreate does not seem to join to the containing transaction - which it what is required (no pun).
Here is the code from #ejbCreate.
getDao()#create gets a JDBC connection and inserts a record into the DB.
public OrderPK ejbCreate (OrderModel aModel)
throws EjbCreateException {
log.debug("EjbCreate " + aModel);
model = aModel;
try {
return getDAO().create(aModel);
} catch(Exception ex) {
throw new EjbCreateException(null,ex,context);