Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: pass (athena.apache.org: domain of curtisr7@gmail.com designates
 209.85.217.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1342809225515-7580677.post@n2.nabble.com>
References: <1342788760352-7580665.post@n2.nabble.com>
	<CAP=qHCtSQQRoLd1gJU=fbKfDjzMmpfnxSQO2fAOBuMOf9JCMYA@mail.gmail.com>
	<1342804153432-7580674.post@n2.nabble.com>
	<CAP=qHCtaKgF=pre3Sb_cvHAUZ367S+j7W_1zfHT7-5X-Tz0ZAg@mail.gmail.com>
	<1342807130289-7580676.post@n2.nabble.com>
	<1342809225515-7580677.post@n2.nabble.com>
Date: Fri, 20 Jul 2012 13:42:43 -0500
Message-ID: 
 <CAP=qHCu==hGJm-ge5cBZ9Wq07XY8UssQcC3tPw-=QK7mCAZoAw@mail.gmail.com>
Subject: Re: Failing to persist a field where the type is
 XMLGregorianCalendar.
From: Rick Curtis <curtisr7@gmail.com>
To: users@openjpa.apache.org
Content-Type: multipart/alternative; boundary=f46d04016ae1f0893804c54742d0

--f46d04016ae1f0893804c54742d0
Content-Type: text/plain; charset=ISO-8859-1

Honestly, I haven't had time to try to run with your customer handlers...

I have been looking ProxyManager code and trying to recreate the initial
stack you posted. Here is a small test you can run to see where it is
blowing up:

XMLGregorianCalendar cc = null; // instantiate me!
OpenJPAEntityManagerFactorySPI emf = (OpenJPAEntityManagerFactorySPI)
getEmf();
emf.getConfiguration().getProxyManagerInstance().newCustomProxy(cc, false);
// this line should fail for you

I haven't been able to recreate the failure on my machine because
org.apache.xerces.jaxp.datatype.XMLGregorianCalendarImpl is a final class
and org.apache.openjpa.util.ProxyManagerImpl<eclipse-javadoc:%E2%98%82=openjpa-kernel/src%5C/main%5C/java%3Corg.apache.openjpa.util%7BProxyManagerImpl.java%E2%98%83ProxyManagerImpl>.generateProxyBeanBytecode(...)
skips trying to create a custom proxy for final types.

Thanks,
Rick

On Fri, Jul 20, 2012 at 1:33 PM, garpinc <garpinc@yahoo.com> wrote:

> It could be that I didn't implement the AbstractValueHandler correctly. The
> api changed from 2.1.2 to 2.2.. now when I restest on 2.1.2 it doesn't work
> where it did before.. Please see if you think they are correct.. In the
> meantime i'll revert to 2.1.2 and put AbstractValueHandler back to how they
> were to see if it then magically works again
>
>
>
> --
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>


-- 
*Rick Curtis*

--f46d04016ae1f0893804c54742d0--