Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: pass (nike.apache.org: domain of kwsutter@gmail.com designates
 209.85.216.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1412696989264-7587176.post@n2.nabble.com>
References: <1412326378581-7587168.post@n2.nabble.com>
 <CABH8erm0jqW20gigaT7SedSbh6Quacr0zbc6w_PBSURgTup3Hw@mail.gmail.com>
 <1412696989264-7587176.post@n2.nabble.com>
From: Kevin Sutter <kwsutter@gmail.com>
Date: Tue, 7 Oct 2014 17:43:16 -0500
Message-ID: 
 <CABH8erkn_aZOC=o=qWSe9jnCzj4OKqN=psw9H7ErBxOnQSaN-Q@mail.gmail.com>
Subject: Re: Moving from OpenJPA 2.0.1 to 2.3.0: fields not found
To: users@openjpa.apache.org
Content-Type: multipart/alternative; boundary=089e012950d809939e0504dcee24

--089e012950d809939e0504dcee24
Content-Type: text/plain; charset=UTF-8

Lionel,
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,
do this...
    mappedBy = "domains",

I know it shouldn't make a difference, but it might isolate the source of
the error if this does work.

Thanks, Kevin

On Tue, Oct 7, 2014 at 10:49 AM, Lionel <lsavouillan@axway.com> wrote:

> Hello,
>
> 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
> process.
> And when I did it, we've seen that there is a maven plugin to do the JPA
> enhancer.
> So that's why :)
>
> I just put back the default PersistenceProviderImpl and sadly, I had the
> same result. :(
>
> <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
>
>
>
> To try to isolate the issue and, tonight, we will just replace the JPA
> version inside the existing project (built with ant) just to validate that
> has really no link with the enhancement.
>
> I will also try to upgrade openJPA version one by one to be sure from which
> the error appears and give additionnal data tomorrow.
>
>
>
> --
> View this message in context:
> http://openjpa.208410.n2.nabble.com/Moving-from-OpenJPA-2-0-1-to-2-3-0-fields-not-found-tp7587168p7587176.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>

--089e012950d809939e0504dcee24--