Manual flush not working

[kimlord]

I am trying to do some post processing after a record is entered into a database and am finding the flush is not causing the record to be written. This is my code:

 @Override
 public String persist() {
 String retval = super.persist();
 EntityManager em = (EntityManager)Component.getInstance("entityManager", true);
 em.flush();
 moveTempRecord();
 return "success";
 }

public void moveTempRecord() {
 log.info("Calling UpdateDB_NID_SUB.loadSubTargetStrength");
 UpdateDB_NID_SUB ACINTDatabase_loader = null;
 ACINTDatabase_loader.loadSubTargetStrength();
 }

In stepping through the code, the problem is that the records are not there for the moveTempRecord method to work. I thought the flush would take care of that. If there is another way to do this, please let me know.

Thank you,
Kim

[kimlord]

This is being called from an EitityHome class created using the Seam generate-entities.

[pmuir]

Mark the persist method @Transactional for a start.

[kimlord]

I did try that and it didn't make a difference.

[kimlord]

The database is Oracle. Does that make a difference?

[kimlord]

This was my last try:

@In EntityManager entityManager;
 @Transactional
 @Begin(flushMode=FlushModeType.MANUAL, join=true)
 public String persist() {
 log.info("Override persist");
 getEntityManager().joinTransaction();
 getEntityManager().persist( getInstance() );

 getEntityManager().getTransaction().commit();
 getEntityManager().flush();
 moveTempRecord();
 return "success";
 }

I have spent all day on this with no luck. I am new to seam so any help is greatly appreciated.
Kim

[fhh]

AFAIK flush() sends the data to the database but does not commit the transaction. So depending on your transaction isolation level you may not be able to see the new records in another transaction.

Regards

Felix