Return-Path: 
 <dev-return-45530-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-dev-archive@www.apache.org
Received: (qmail 38460 invoked from network); 7 Feb 2007 01:35:02 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 7 Feb 2007 01:35:02 -0000
Received: (qmail 82800 invoked by uid 500); 7 Feb 2007 01:35:07 -0000
Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org
Received: (qmail 82757 invoked by uid 500); 7 Feb 2007 01:35:07 -0000
Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@geronimo.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@geronimo.apache.org>
List-Post: <mailto:dev@geronimo.apache.org>
Reply-To: dev@geronimo.apache.org
List-Id: <dev.geronimo.apache.org>
Delivered-To: mailing list dev@geronimo.apache.org
Received: (qmail 82746 invoked by uid 99); 7 Feb 2007 01:35:07 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Feb 2007 17:35:06 -0800
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: local policy)
Received: from [208.97.132.145] (HELO spaceymail-a2.g.dreamhost.com)
 (208.97.132.145)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Feb 2007 17:34:56 -0800
Received: from [192.168.15.102] (cpe-76-167-174-30.socal.res.rr.com
 [76.167.174.30])
	by spaceymail-a2.g.dreamhost.com (Postfix) with ESMTP id 13B4610618B
	for <dev@geronimo.apache.org>; Tue,  6 Feb 2007 17:34:33 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <E0D7F605-3834-4971-966C-BAF8BFE45ED4@iq80.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: dev <dev@geronimo.apache.org>
From: Dain Sundstrom <dain@iq80.com>
Subject: Global JNDI effectively required for Jee5
Date: Tue, 6 Feb 2007 17:34:13 -0800
X-Mailer: Apple Mail (2.752.3)
X-Virus-Checked: Checked by ClamAV on apache.org

Jee5 makes extensive use of Global JNDI for references.   
Specifically, the following use Global JNDI:

@Resource.mappedName()
This mapped name is often a global JNDI name, but may be a name of  
any form.

@EJB.mappedName()
This mapped name is often a global JNDI name, but may be a name of  
any form.

@MessageDriven.mappedName()
A product specific name(e.g. global JNDI name of a queue) that this  
message-driven bean should be mapped to.

@WebServiceRef.mappedName()
This mapped name is often a global JNDI name, but may be a name of  
any form.

<persistence-unit><jta-data-source>
<persistence-unit><non-jta-data-source>
InJavaEEenvironments,thejta-data-sourceandnon-jta-data- 
sourceelementsareused
tospecifytheglobal JNDInameoftheJTAand/ornon- 
JTAdatasourcetobeusedbythepersistence
provider.


The spec makes it clear that Global JNDI is not required to satisfy  
these values, and that the meaning of these fields is completely  
vendor specific.  In the case of mapped name, the application server  
can completely ignore the field.

The problem is our users' applications will make use of mapped name  
in other application servers, and since every application server that  
I know if is implementing these with Global JNDI, it becomes a  
defacto standard and requirement for Jee5.  Moreover, I believe that  
our GlobalJNDI names must be simple normal names (i.e, not encoded  
abstract names) you would see in other application servers, because  
users will annotate their code with the mapped names, effectively  
locking in the Global JNDI names that they expect to work in our  
application server.

So do you agree that Global JNDI is the defacto required  
implementation for these and other similar entries?

-dain