Found an answer to my question, apparently a minor bug in OpenJPA (
https://issues.apache.org/jira/browse/OPENJPA-2401), in which XML
configuration is not being consulted when deciding to print that warning
message.
Glen
On 06/13/2013 10:01 PM, Glen Mazza wrote:
Hi, I'm new to OpenJPA (and JP
Hi Kevin
I think that OpenJPA is great and the way it stuck to JPA 2.0 Standard
so quick was very good. As I am looking more and more into the JEE and
the desktop side of things is just as important to me, world it would be
great to keep the provider I know so well. I am may even be able to h
Hi Matthew,
I greatly appreciate your insights. And, I'm 100% behind you on this.
OpenJPA has a great, large set of users. We get feedback from all facets
of the industry and we try to respond to the best of our ability. Like the
squeaky wheel, we pay the most attention to those areas requesting
Thanks Kevin,
I tried setting the QuerySQLCache to false but that didn't seem to fix the
issue. I am still seeing those exceptions.
Does it have to do anything with class loaders or maybe something with the
way I currently have setup my parent-child relations
As mentioned before it works fine if t
You could set the property openjpa.DetachState(DetachedStateField=true). This
property will make our DetachedStateManager serializeable and then the JPA
runtime can 'track' a detached Entity. The only down side to this approach
is that the OpenJPA classes must be on the classpath of the client that
I'm not sure if this is a bug or if my understanding of the way how it
should work is wrong. Maybe someone can help me out a little bit.
In an application (WebSphere 8.0.0.5, OpenJPA 2.1.2) I need to get the
generated native SQL String from an JPQL to manipulate it. It is working
great but when
