Return-Path: 
 <user-return-6064-apmail-geronimo-user-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-user-archive@www.apache.org
Received: (qmail 3071 invoked from network); 22 Feb 2007 23:15:35 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 22 Feb 2007 23:15:35 -0000
Received: (qmail 26431 invoked by uid 500); 22 Feb 2007 23:15:41 -0000
Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org
Received: (qmail 26410 invoked by uid 500); 22 Feb 2007 23:15:41 -0000
Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:user-help@geronimo.apache.org>
list-unsubscribe: <mailto:user-unsubscribe@geronimo.apache.org>
List-Post: <mailto:user@geronimo.apache.org>
Reply-To: user@geronimo.apache.org
List-Id: <user.geronimo.apache.org>
Delivered-To: mailing list user@geronimo.apache.org
Received: (qmail 26398 invoked by uid 99); 22 Feb 2007 23:15:41 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Feb 2007 15:15:41 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of gcjgu-user@m.gmane.org
 designates 80.91.229.2 as permitted sender)
Received: from [80.91.229.2] (HELO ciao.gmane.org) (80.91.229.2)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Feb 2007 15:15:29 -0800
Received: from root by ciao.gmane.org with local (Exim 4.43)
	id 1HKN9S-0005Gu-El
	for user@geronimo.apache.org; Fri, 23 Feb 2007 00:15:02 +0100
Received: from ip-209-134-174-86.iss.net ([209.134.174.86])
        by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <user@geronimo.apache.org>; Fri, 23 Feb 2007 00:15:02 +0100
Received: from pgrey by ip-209-134-174-86.iss.net with local (Gmexim 0.1
 (Debian))
        id 1AlnuQ-0007hv-00
        for <user@geronimo.apache.org>; Fri, 23 Feb 2007 00:15:02 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: user@geronimo.apache.org
From: "pgrey" <pgrey@iss.net>
Subject: Re: ejb circular references
Date: Thu, 22 Feb 2007 18:06:15 -0500
Lines: 55
Message-ID: <erl7l7$ki7$1@sea.gmane.org>
References: <A99F00E9A39CF5428039DE37B2069B2104B49464@atlmaiexcp02.iss.net>
 <235FAA12-810B-4CAF-975A-8A66357100A1@yahoo.com>
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: ip-209-134-174-86.iss.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Sender: news <news@sea.gmane.org>
X-Virus-Checked: Checked by ClamAV on apache.org

Yes, we have run into a problem.

The EJBs are in different EARs.

> If you ejbs are in different ears, things get a bit trickier.  IIRC  you 
> have to supply the entire  abstract name of the ejb container  gbean for 
> at least one side of the relationship.

Can you give an example of "supply the entire abstract name of the ejb 
container gbean"?

Thank you kindly.


"David Jencks" <david_jencks@yahoo.com> wrote 
in message news:235FAA12-810B-4CAF-975A-8A66357100A1@yahoo.com...
>
> On Feb 22, 2007, at 12:24 PM, Spotts, Joel ((ISS Atlanta)) wrote:
>
>> I have a bit of a predicament with circular refrences in EJBs. Due  to 
>> legacy reasons, I have two EJBs - each which references the  other (and 
>> refactoring would be non-trivial). I would prefer to  keep them local (as 
>> opposed to remote) for security reasons.  Trouble is, I don't know how to 
>> deploy such an arrangement in  geronimo. Each EJB will need to reference 
>> the other in openejb- jar.xml with an <ejb-ref> stanza. But since each 
>> one is dependent  on the other, each one cannot be deployed before the 
>> other (as  geronimo checks for the ejb reference at deploy time). Without 
>> violated some accepted principals of physics, that leads to an 
>> impossible situation. How could I go about solving this issue?
>
> This is supposed to work easily, at least if the ejbs are in the same 
> ear.  Deployment goes in phases: in "initContext" we try to find out  and 
> "publish" all the things you could possibly reference, such as  ejbs and 
> datasources.  Then in "addGBeans" we process the jndir ref  info and 
> construct the jndi References to the appropriate stuff.  For  ejbs in the 
> same ear, all necessary info should have been "published"  and thus 
> available.
>
> If you ejbs are in different ears, things get a bit trickier.  IIRC  you 
> have to supply the entire  abstract name of the ejb container  gbean for 
> at least one side of the relationship.
>
> Are you speculating or have you actually run into a problem :-)?
>
> thanks
> david jencks
>
>>
>> Thanks,
>>
>> Yoel Spotts
>
>