Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (athena.apache.org: domain of michael.d.dick@gmail.com
 designates 209.85.218.46 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=opV2X6SWQ/gQAW+KnPAlz3WuUxcXVUoQ/xtenYFCiPF74ImFl33+421Cw9c/5sZKkE
         Adxuz3lxtLh4htisqXIkEMSFFsW9GzqrMjpvN4jX3Vsuquu/j99B9HcT6qkuIe3ukXrl
         epygv3HwE4BqXZ7EbNYtmAsUsnzPdaZ9J0QjY=
MIME-Version: 1.0
In-Reply-To: <9E3A9D23-7DC8-4819-8060-1C67CB07B6AC@oracle.com>
References: <1301435466265-6221096.post@n2.nabble.com>
 <AANLkTinoXki9oP7TPZ-4K2eUG9rDEsJavta3bWoRUbLN@mail.gmail.com>
 <9E3A9D23-7DC8-4819-8060-1C67CB07B6AC@oracle.com>
From: Michael Dick <michael.d.dick@gmail.com>
Date: Tue, 29 Mar 2011 21:55:21 -0500
Message-ID: <AANLkTi=kj0OOyN6Vc70HNg-9qYMJXis3nsQS5EAhd6mx@mail.gmail.com>
Subject: Re: About DataCache and RemoteCommitProvider in application server
 context.
To: dev@openjpa.apache.org
Content-Type: multipart/alternative; boundary=001485f90f98ef10fc049faa4fa9

--001485f90f98ef10fc049faa4fa9
Content-Type: text/plain; charset=ISO-8859-1

If you used the JMS provider you could configure a separate topic for each
PU, or with the TCP provider use a different port. There would be some more
set up to be done (e.g. configuring JMS) but is should isolate the events.

You can't avoid the RemoteCommitProvider entirely - it's required when using
a DataCache (it'll throw an exception when you create an EMF).

The documentation is a little light, but having each EMF listen to a
different topic / port should get you started down the right path.

-mike

On Tue, Mar 29, 2011 at 9:25 PM, Ravi Palacherla <ravi.palacherla@oracle.com
> wrote:

> Thanks Mike.
>
> So, if I use JMS RemoteCommitProvider and not configure it properly then
> the events will not be fired ?
> Can I completely avoid using Remote commit provider ?
> Will it have any effect on datacache ?
>
> I believe I can avoid RemoteCommitProviders and still use datacache with
> out any issues, correct ?
>
> I am using JPA1.0 hence any JPA2.0 solutions wont work.
>
> Regards,
> Ravi.
>
> On Mar 29, 2011, at 8:15 PM, Michael Dick wrote:
>
> > Short answer: you might have to use the JMS or TCP RemoteCommitProviders
> if
> > you don't want the events to be fired.
> >
> > Long answer: The SJVM  RemoteCommitProvider uses a static HashSet to keep
> > track of all of it's instances and broadcasts events to all of them.
> There's
> > no filtering built in. You could write a RemoteCommitProvider that was
> aware
> > of the list of persistent types though, but that function isn't available
> > right now.
> >
> > It might also work to configure the cache to only accept certain entities
> > via configuration options, JPA 2.0 annotations, or the
> PartitionedDataCache
> > (since OpenJPA 2.0.0).
> >
> > Hope this helps,
> > -mike
> >
> > On Tue, Mar 29, 2011 at 4:51 PM, Ravi P Palacherla <
> > ravi.palacherla@oracle.com> wrote:
> >
> >> Hi ,
> >>
> >> I have two different EJBs each has its own persistence units
> >> (persistence.xml) and deployed as two different applications. Both have
> >> DataCache enabled and RemoteCommitProvider set to sjvm.
> >> Committing EntityA in EJBA results in broadcasting this event to event
> >> manager in EJBB.
> >> As EntityA is not present in EJBB, it results in ClassNotFoundException
> of
> >> EntityA.
> >>
> >> How can I avoid events (commits) for entities in EJBA to be broadcasted
> to
> >> event manager in EJBB ?
> >>
> >> Regards,
> >> Ravi.
> >>
> >> --
> >> View this message in context:
> >>
> http://openjpa.208410.n2.nabble.com/About-DataCache-and-RemoteCommitProvider-in-application-server-context-tp6221096p6221096.html
> >> Sent from the OpenJPA Developers mailing list archive at Nabble.com.
> >>
>
>

--001485f90f98ef10fc049faa4fa9--