No there are no exceptions. And enabling openjpa.Log Enhance=TRACE did not
help either.
But I did some debugging and I could isolate the problem.
When I persist my entities I do a flush and a refresh in order to return the
entity instance just after the INSERT to the client. This is done because
Is OSIV with a stateful EJB reliable? What happens, when under load (or
otherwise), the container decides to passivate the stateful bean. Would that
event be completely transparent to a conversation that is using the bean,
the PC, and managed entities therein?
The Seam project appears to
On Tue, Jul 26, 2011 at 6:02 AM, M. Walter marc.wal...@sbb.ch wrote:
I did the following:
final OpenJPAQuery ojpaQuery =
OpenJPAPersistence.cast(em.createNamedQuery(
StammdatenQueryNames.FIND_ALL_BP.name()));
ojpaQuery.getFetchPlan().removeFetchGroup(FetchGroup.NAME_DEFAULT);
I don't have a nice solution for you (at least not yet).
I may have an explanation for the warning that you're getting. The
javaAccessorNotSet can happen if a JNDI namespace is not available. In this
case the JPA code is looking for the Transaction Synchronization Registry in
JNDI, but it's not
perhaps http://jpasecurity.sourceforge.net/
can help you to control access as JPA xxtension, but it's more for security
auditing than just logging
regards
Frank
--
View this message in context:
http://openjpa.208410.n2.nabble.com/Audit-log-with-OpenJPA-tp6557932p6632956.html
Sent from the
Interesting - will definitely take a look.
/Bengt
Den 29 jul 2011 19:24 skrev pif frank.pien...@googlemail.com:
perhaps http://jpasecurity.sourceforge.net/
can help you to control access as JPA xxtension, but it's more for
security
auditing than just logging
regards
Frank
--
View this
