Re: javax.persistence.EntityListeners is never called

2014-10-14 Thread gouessej
Hi One of the classes seems to be parsed twice according to the trace: 718 RCSDMWebServicesPU TRACE [main] openjpa.MetaData - Loading metadata for "class com.**.*.ejbs.utils.MultiLangString" under mode "[META][QUERY]". 718 RCSDMWebServicesPU TRACE [main] openjpa.MetaData - Parsing class

Re: javax.persistence.EntityListeners is never called

2014-10-14 Thread gouessej
I use OpenJPA 2.4.0. I'm going to try with a more recent version if any. > Message du 14/10/14 00:14 > De : "Kevin Sutter" > A : users@openjpa.apache.org, goues...@orange.fr > Copie à : > Objet : Re: javax.persistence.EntityListeners is never called > > Hi, > The complete trace can be turn

Re: javax.persistence.EntityListeners is never called

2014-10-14 Thread Kevin Sutter
Hi, Your p.xml didn't post correctly... I'm curious what the NONE setting is for... At this point, nothing else is jumping out at me... Kevin On Tue, Oct 14, 2014 at 4:30 AM, wrote: > Hi > > One of the classes seems to be parsed twice according to the trace: > 718 RCSDMWebServicesPU TRACE [mai

Re: javax.persistence.EntityListeners is never called

2014-10-14 Thread Rick Curtis
2.4.x is the latest. If I understand your previous posts, are you using callbacks(@Preload, @Postload, etc, etc) on an Embeddable? If that is the case, I'm not sure if it is suppose to work? Can I have you post some Entity/embeddable snippets so we can better understand what you want to do? Thank

Re: javax.persistence.EntityListeners is never called

2014-10-14 Thread gouessej
Sorry for the confusion. No I'm not using those callbacks on an Embeddable but when I switched to OpenJPA, I remember that I had to add the classes with @Embeddable into persistence.xml whereas it wasn't necessary with Hibernate. The class that uses those callbacks uses the annotation @Singleton

Re: javax.persistence.EntityListeners is never called

2014-10-14 Thread Rick Curtis
One thing that jumps out of your p.xml is the openjpa.Multithreaded property. I suggest you get rid of that property and ensure that you aren't sharing EntityManager's across threads... but I don't think that is related to the problem you are currently having. Can you post relevant snippets of you