Re: [eclipselink-users] DescriptorCustomizer and Spring-Data

[Luciano Santos <greiner.luciano@xxxxxxxxx>]

Hi Tom, thanks for the trick. There was a hidden RuntimeException happening on my Customizer implementation, but the processing continues, so at some point everything falled apart. But it's working now, except for that Tenant problem i just raised.

Thanks

2013/6/11 Tom Ware <tom.ware@xxxxxxxxxx>

Currently, by default some of the EntityManager initialization occurs at first use.  Maybe that is affecting what is happening.  Try setting the following persistence unit property:

eclipselink.deploy-on-startup=true

On 10/06/2013 2:30 AM, Luciano Santos wrote:

Hello.

i am migrating an application from Hibernate to EclipseLink. We do use the
latest Spring Data to generate some repositories.

I have created a global DescriptorCustomizer implementation which is applied
into all classes to iterate over the fields and apply some converters.

Although, it seems that there's some async processing for this customizer,
because spring is being able to use the EntityManager before the customization
is applied into the whole mapping, so then i

Shouldn't the EntityManager be available just after all processing? Is there a
way to force it?

Any thoughts?

Thanks

Luciano G Santos

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

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