From dev-return-18821-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Wed Mar 30 02:16:29 2011 Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 48068 invoked from network); 30 Mar 2011 02:16:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 30 Mar 2011 02:16:28 -0000 Received: (qmail 27553 invoked by uid 500); 30 Mar 2011 02:16:28 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 27509 invoked by uid 500); 30 Mar 2011 02:16:28 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 27501 invoked by uid 99); 30 Mar 2011 02:16:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Mar 2011 02:16:28 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of michael.d.dick@gmail.com designates 209.85.160.174 as permitted sender) Received: from [209.85.160.174] (HELO mail-gy0-f174.google.com) (209.85.160.174) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Mar 2011 02:16:24 +0000 Received: by gyd10 with SMTP id 10so447329gyd.33 for ; Tue, 29 Mar 2011 19:16:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=ZcKtYaFBpi5csqbA+4oij1shDRbmjiWQNkm0HqAMLws=; b=sMqanzdkaJ+aOVo7diMLUCiElwZcjF3YVmNOHgn+ZKiuye5eZ/xxh6E1WbnYxyPk0i r++X+vr4XW+iA8Zdl8joEnMRCrL3al+iQwM88qwTmXL18f+g9ScYmccjJvLkQhcGTimm AW/XD5ayj/EzA5oLEaABiUbm+lN00HhPdgG4o= 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=wac44JCBB0JtI6srowJwcFlnw3bhbCiQEIoZ051blv+OVeLxaeZrm9x5hXfFO23yki 2qAc+0yddalH3S9SbZq19+QkB+a0qpfEcm/dxnYLyLtnJq8xs2KpvXt4nBK/RtS0n4eM aT9zeZ1CsKSCJ6+eYHlZnOFbFmAlZTLdMACXo= Received: by 10.91.32.36 with SMTP id k36mr78141agj.176.1301451362128; Tue, 29 Mar 2011 19:16:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.90.80.1 with HTTP; Tue, 29 Mar 2011 19:15:42 -0700 (PDT) In-Reply-To: <1301435466265-6221096.post@n2.nabble.com> References: <1301435466265-6221096.post@n2.nabble.com> From: Michael Dick Date: Tue, 29 Mar 2011 21:15:42 -0500 Message-ID: Subject: Re: About DataCache and RemoteCommitProvider in application server context. To: dev@openjpa.apache.org Content-Type: multipart/alternative; boundary=001485f90f9821d2ab049fa9c2cc --001485f90f9821d2ab049fa9c2cc Content-Type: text/plain; charset=ISO-8859-1 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. > --001485f90f9821d2ab049fa9c2cc--