> or do I need to set the row-locking to
> true for the bean in jbosscmp-jdbc? (I tried this,
> but it didn't deploy properly with this line added).
> Or do I need to do something else???
Sorry, I made a mistake in the jbosscmp-jdbc file. It now deploys and the bean uses row-locking.
**HOWEVER** my original problem remains :( Any suggestions?
First, only session and message driven beans can define transaction type. All entities have transaction-type Container by the spec.
As to your problem, are you sure the transaction that removed entity is finished before the findAll is called?
> First, only session and message driven beans can
> define transaction type.
Sorry, I think I mislead you in my original post. I am using a session bean, with user transactions. These transactions call methods on CMP Entity beans.
> All entities have
> transaction-type Container by the spec.
> As to your problem, are you sure the transaction that
> removed entity is finished before the findAll is
No, I don't think it is. I believe that is the problem ... I want the database to locked until the first transaction completes. I'm not sure what I need to set for this to happen in JBoss?
If you mean transaction serialization it is set up in data source configuration. You can look at examples for, say, Oracle.
Or post your questions in the jboss use list. I don't have much experience with it.