Re: [eclipselink-users] JAXB having problems marshaling entity due to we

[Tom Ware <tom.ware@xxxxxxxxxx>]

Hi Laird,

  The code we use to add the XMLTransient annotation checks the JPA mapping 
first to see if it uses Property access.  It may be possible that a JPA Lazy x-1 
using property access would cause a problem if JAXB was somehow using FIELD 
access.

  Does that help you narrow down the issue?

-Tom

On 13/02/2013 3:05 PM, Laird Nelson wrote:
> Dynamic as provided by GlassFish 3.1.2.2.
>
> I cannot supply the class at the moment.  I can tell you that it features a
> mapped superclass in it if that helps.  It also features explicit
> @Access(AccessType.FIELD) at the class level, and a single
> @Access(AccessType.PROPERTY) on one property.  This does not seem to be the
> property whose VH field is the troublemaker.
>
> Best,
> Laird
>
>
> On Wed, Feb 13, 2013 at 10:47 AM, Tom Ware <tom.ware@xxxxxxxxxx
> <mailto:tom.ware@xxxxxxxxxx>> wrote:
>
>     Hi Laird,
>
>        We attempt to weave XMLTransient on to those fields.  Can you provide a
>     sample class so we can see why it is not showing up?
>
>     BTW: Are you using dynamic weaving or static weaving?
>
>     -Tom
>
>
>     On 13/02/2013 10:02 AM, Laird Nelson wrote:
>
>         Good morning; we're getting the following exception when one of our
>         EclipseLink-woven entities is being marshaled by JAXB:
>
>
>         org.eclipse.persistence.__indirection.__WeavedAttributeValueHolderInte__rface
>         is
>              an interface, and JAXB can't handle interfaces.
>
>                               this problem is related to the following location:
>
>                                               at
>
>         org.eclipse.persistence.__indirection.__WeavedAttributeValueHolderInte__rface
>
>                                               at protected
>
>         org.eclipse.persistence.__indirection.__WeavedAttributeValueHolderInte__rface
>
>         com.jenzabar.ngp.financial.__accounting.jpa.JournalEntity.___persistence___reconcileGeneralLedger_vh
>
>         I am deeply and unfortunately familiar :-) with the fact that JAXB can't
>         deal
>         with interfaces, so I understand the error from that end of things.
>
>         But I don't know how to work around this issue.  The mighty Google produces
>         exactly one result (!) that is similar to mine:
>         http://www.eclipse.org/forums/__index.php/m/531683/
>         <http://www.eclipse.org/forums/index.php/m/531683/>
>
>         In our case we are not using EclipseLink annotations at all--straight JPA.
>
>         Is this what happens when lazy-loaded fields bump into JAXB marshaling?
>
>         Thanks,
>         Laird
>
>         --
>         http://about.me/lairdnelson
>
>
>         _________________________________________________
>         eclipselink-users mailing list
>         eclipselink-users@xxxxxxxxxxx <mailto:eclipselink-users@xxxxxxxxxxx>
>         https://dev.eclipse.org/__mailman/listinfo/eclipselink-__users
>         <https://dev.eclipse.org/mailman/listinfo/eclipselink-users>
>
>     _________________________________________________
>     eclipselink-users mailing list
>     eclipselink-users@xxxxxxxxxxx <mailto:eclipselink-users@xxxxxxxxxxx>
>     https://dev.eclipse.org/__mailman/listinfo/eclipselink-__users
>     <https://dev.eclipse.org/mailman/listinfo/eclipselink-users>
>
>
>
>
> --
> http://about.me/lairdnelson
>
>
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-users