Craig,
I'm not an expert with namespaces, but it would be something along the lines
of first defining the openjpa namespace and then specifying the attributes
qualified by this namespace. We would also need to provide a schema for
this openjpa namespace. Something like this, following on from
Hi Kevin,
I'm not either an expert in namespaces, which is why I didn't follow
in the first place ;-)
On Jan 16, 2007, at 6:12 AM, Kevin Sutter wrote:
Craig,
I'm not an expert with namespaces, but it would be something along
the lines
of first defining the openjpa namespace and then
I have defined JDBC SavepointManager in my persistence.xml.I am running
against DB2 v9
property name=openjpa.SavepointManager value=jdbc/
Now a run a test client as follows
EntityManagerFactory emf = Persistence.
*
createEntityManagerFactory* (dwtest);
EntityManager em =
That indeed does sound like a better solution.
On Jan 16, 2007, at 6:12 AM, Kevin Sutter wrote:
Craig,
I'm not an expert with namespaces, but it would be something along
the lines
of first defining the openjpa namespace and then specifying the
attributes
qualified by this namespace. We
Any input is this a bug or do I need to set auto-commit to
false.If so how
do I do that?
Normally, OpenJPA should set autocommit to false automatically. This
will not happen in certain situations (such as when OpenJPA is used in a
JTA context). Can you post your full configuration file so we
Try performing a persistence operation (persisting an entity,
changing a persistent entity, deleting an entity, etc) before setting
the savepoint. It could just be a bug with empty savepoints in
optimistic transactions (which aren't too useful anyway).
you were right by setting Savepoint after some persistence operation seems
to fix the problem
thanks
ritika
On 1/16/07, Abe White [EMAIL PROTECTED] wrote:
Try performing a persistence operation (persisting an entity,
changing a persistent entity, deleting an entity, etc) before setting
the
You'll also want to set ConnectionRetainMode to transaction, which
will
ensure that OpenJPA has a single connection for the duration of the
transaction.
Performing a persistence operation and then setting a savepoint is
enough to ensure you keep the same connection, regardless of the
Hi,
I've tried several thing:
- First I made sure that the tx was started when I get the EntityManager.
- Second I've tried calling em.joinTransaction() while the transaction is
being executed, didn't change anything.
- Lastly I've tried to call em.flush() before commit and got the following:
Looking for some assistance (that is, background information) on how the
orm.xml parsing is supposed to work. I'm attempting to specify some entity
listeners in my orm.xml, but I continue to get the following TRACE message:
322664 my persistence unit TRACE [main] openjpa.MetaData - OpenJPA
JTA transaction rollback, nonexistant instances, transactional persistence
context = failures during afterCompletion() and close()
---
Key: OPENJPA-102
[
https://issues.apache.org/jira/browse/OPENJPA-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-102:
Attachment: openjpa-detach.patch
JTA transaction rollback, nonexistant instances,
12 matches
Mail list logo
