Re: [eclipselink-users] Another converter-bug

[Guy Pelletier <guy.pelletier@xxxxxxxxxx>]

Adding the customizer to the MappedSuperclass should have worked. That is, that customizer class should be applied to all subclasses. I'll have a look and see what the issue could be there as well.

Cheers,
Guy

On 05/07/2013 5:22 PM, Andreas Joseph Krogh wrote:

På fredag 05. juli 2013 kl. 22:44:27, skrev Andreas Joseph Krogh <andreak@xxxxxxxxxxxx>:

På fredag 05. juli 2013 kl. 21:31:43, skrev Andreas Joseph Krogh <andreak@xxxxxxxxxxxx>:

På fredag 05. juli 2013 kl. 20:59:27, skrev Guy Pelletier <guy.pelletier@xxxxxxxxxx>:

Hi Andreas,

I pin pointed the problem internally and will look to have a fix in place soon.

[snip]

 

Hm, it turns out it doesn't quite work for attributes defined in a @MappedSuperclass.

I have "modified" (as a CustomOptional<DateTime>) in a @MappedSuperclass and annotating it with a customizer which customizes its "modified"-attribute doesn't work.

 

Is the only work-around to not have "modified" in the @MappedSuperclass and create customizers for all sub-entities?

 

Customizing the "modified"-attribute (defined in the @MappedSuperclass) using a customizer for the child-entity works.

 

Will your planned fix also take care of this?

 

 

--
Andreas Joseph Krogh <andreak@xxxxxxxxxxxx>      mob: +47 909 56 963
Senior Software Developer / CTO - OfficeNet AS - http://www.officenet.no
Public key: http://home.officenet.no/~andreak/public_key.asc

 

_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users

--

Guy Pelletier

ORACLE Canada, 45 O'Connor Street Suite 400 Ottawa, Ontario Canada K1P 1A4
Oracle is committed to developing practices and products that help protect the environment