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 av
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
t
Hi,
Is there an exception logged with the message? The inner message is an INFO
message, so in itself it should be benign. I'd expect the Transaction
Synchronization Registry to only be available in JEE, so I don't think there
is anything wrong with your environment.
I'm at a loss regarding the j
