> >
> >
> >
> >
> >
> >
> >
> >
> >
> > . . .
> >
> > Is that more what you're looking for?
> >
> > -mike
> >
> >
> >
> >
>
> --
> View this message in context:
> http://n2.nabble.com/regarding-StoreListener-tp2420847p2425189.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>
>
> class="org.apache.openjpa.persistence.annotations.common.apps.annotApp.ddtype.DefaultCallbackListener">
>
>
>
>
>
>
>
>
>
>
>
>
er to.
> >>
> >> The problem is that I think this way of adding listeners is not correct.
> >> I've already used Hibernate and they have a simple XML file in which you
> >> can
> >> simply define your desired listeners and they are guaranteed to work
> each
> >> time a CRUD operation being applied
> >> Is there anythink like that in OpenJPA or Do we need to open an issue in
> >> JIRA and request such feature?
> >>
> >> thanks
> >> --
> >> View this message in context:
> >> http://n2.nabble.com/regarding-StoreListener-tp2420847p2420847.html
> >> Sent from the OpenJPA Users mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://n2.nabble.com/regarding-StoreListener-tp2420847p2424814.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>
>
>> simply define your desired listeners and they are guaranteed to work each
>> time a CRUD operation being applied
>> Is there anythink like that in OpenJPA or Do we need to open an issue in
>> JIRA and request such feature?
>>
>> thanks
>> --
>> View
gt; Is there anythink like that in OpenJPA or Do we need to open an issue in
> JIRA and request such feature?
>
> thanks
> --
> View this message in context:
> http://n2.nabble.com/regarding-StoreListener-tp2420847p2420847.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>
>
ple XML file in which you can
simply define your desired listeners and they are guaranteed to work each
time a CRUD operation being applied
Is there anythink like that in OpenJPA or Do we need to open an issue in
JIRA and request such feature?
thanks
--
View this message in context:
http://n2.nabbl
