Re: Moving from OpenJPA 2.0.1 to 2.3.0: fields not found
I would suggest trying to turn on Trace, but there doesn't seem to be a lot
of tracing in this particular area of the code... It still might be
worth a shot. Maybe an earlier log entry might shed some light on why this
is going awry...
I'm going to suggest one quick change just to see if it makes a
difference. It shouldn't, but I stumbled on this the first time I read
your code, so maybe the OpenJPA code is making the same mistake...
Instead of referencing a final String field for your mappedBy field, what
happens if you just insert the actual string? For example, instead of...
mappedBy = CAService._domainFieldName,
mappedBy = "domains",
I know it shouldn't make a difference, but it might isolate the source of
the error if this does work.
On Tue, Oct 7, 2014 at 10:49 AM, Lionel <lsavouillan@...> wrote:
> First, thanks a lot for your answer. :)
> In the past, we were using an ant build the project so also to run the JPA
> enhancer but for a company strategy reason we are moving to a maven build