Return-Path: 
 <user-return-954-apmail-geronimo-user-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-user-archive@www.apache.org
Received: (qmail 28641 invoked from network); 18 Oct 2005 18:59:28 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 18 Oct 2005 18:59:28 -0000
Received: (qmail 66042 invoked by uid 500); 18 Oct 2005 18:59:26 -0000
Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org
Received: (qmail 66012 invoked by uid 500); 18 Oct 2005 18:59:25 -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 66001 invoked by uid 99); 18 Oct 2005 18:59:25 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Oct 2005 11:59:25 -0700
X-ASF-Spam-Status: No, hits=0.5 required=10.0
	tests=DNS_FROM_RFC_ABUSE
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [66.163.169.227] (HELO smtp107.mail.sc5.yahoo.com)
 (66.163.169.227)
    by apache.org (qpsmtpd/0.29) with SMTP; Tue, 18 Oct 2005 11:59:25 -0700
Received: (qmail 18104 invoked from network); 18 Oct 2005 16:57:08 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Received:Mime-Version:In-Reply-To:References:Content-Type:Message-Id:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer;
  b=hYDzWdkgAanD+tmXgQkagRThD2NH5aDkY+xmjWu3vt9UxFP7uwri5aORUSumL7Q36GlUvfXsfgXEIUFC+8PlWFbA1sjJETfkLCeOff+HM2fls+YxbIhzmXIpfJxUS5hckcz+F35qHxLgmIflH+5GtM5aH0GOe6kZeKb8Bc8mEyk=
  ;
Received: from unknown (HELO ?192.168.1.5?) (david?jencks@66.93.38.137 with
 plain)
  by smtp107.mail.sc5.yahoo.com with SMTP; 18 Oct 2005 16:57:08 -0000
Mime-Version: 1.0 (Apple Message framework v622)
In-Reply-To: 
 <OFB2061785.FC596A39-ON8525709E.0053BA9D-8525709E.00546D94@ca.ibm.com>
References: 
 <OFB2061785.FC596A39-ON8525709E.0053BA9D-8525709E.00546D94@ca.ibm.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <9f73b3b191e74a49cc32a43bb6031568@yahoo.com>
Content-Transfer-Encoding: 7bit
From: David Jencks <david_jencks@yahoo.com>
Subject: Re: Geronimo M5 JNDI resources
Date: Tue, 18 Oct 2005 09:57:04 -0700
To: user@geronimo.apache.org
X-Mailer: Apple Mail (2.622)
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N


On Oct 18, 2005, at 8:22 AM, Richard Duggan wrote:

>
> I would like to create some JNDI resources that can be configured as 
> part
> of a configuration file.   Using Tomcat this can be achieved by 
> configuring
> the resource factory in the server.xml file (as shown below).  How is 
> it
> recommended that this be achieved with Geronimo?  I initially had two
> thoughts, either this could be hosted by the embedded Tomcat and 
> configured
> using the geronimo-web.xml file it could be hosted as part of the 
> openejb
> component and configured using the openejb-jar.xml.  Can anyone share 
> some
> advise?
>
>
>
>
>
>
>
>
>
>
>
>   <Context ...>
>     ...
>     <Resource name="bean/MyBeanFactory" auth="Container"
>               type="com.mycompany.MyBean"/>
>     <ResourceParams name="bean/MyBeanFactory">
>       <parameter>
>         <name>factory</name>
>         <value>org.apache.naming.factory.BeanFactory</value>
>       </parameter>
>       <parameter>
>         <name>bar</name>
>         <value>23</value>
>       </parameter>
>     </ResourceParams>
>     ...
>   </Context>
>
>

On first look, I would say this is not a use of jndi supported by the 
j2ee spec, and that there is no direct support in geronimo for it at 
this time.  I'd be interested in knowing more about what you are trying 
to do here and what the result of the jndi lookup is supposed to be.  
It looks like you are trying to expose a javabean in jndi, each lookup 
returning a new instance?  The configuration of the javabean factory 
could be done easily as a gbean, but there would be no direct way to 
access it in jndi.  We've discussed possible ways of exposing arbitrary 
gbeans through jndi but due to lack of clear use cases and time nothing 
is implemented at the moment.

As workarounds you might be able to use env-entries to let your j2ee 
component construct the javabean itself or you might possibly be able 
to do something by registering a custom URL handler that would create 
the javabean for you.

thanks
david jencks