Return-Path: 
 <dev-return-72845-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-dev-archive@www.apache.org
Received: (qmail 4032 invoked from network); 26 Mar 2009 10:20:17 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 26 Mar 2009 10:20:17 -0000
Received: (qmail 44735 invoked by uid 500); 26 Mar 2009 10:20:16 -0000
Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org
Received: (qmail 44656 invoked by uid 500); 26 Mar 2009 10:20:16 -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 44624 invoked by uid 99); 26 Mar 2009 10:20:16 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Mar 2009 10:20:16 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Mar 2009 10:20:14 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 6225E234C046
	for <dev@geronimo.apache.org>; Thu, 26 Mar 2009 03:19:53 -0700 (PDT)
Message-ID: <1145853686.1238062793401.JavaMail.jira@brutus>
Date: Thu, 26 Mar 2009 03:19:53 -0700 (PDT)
From: "David Jencks (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-3954) Allow overriding the value of an
 <env-entry/> from within deployment plans
In-Reply-To: <384553394.1207640605583.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/GERONIMO-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689421#action_12689421 ] 

David Jencks commented on GERONIMO-3954:
----------------------------------------

Also I'm not sure if openejb is using the geronimo env-entry builder -- this change may not affect openejb.

> Allow overriding the value of an <env-entry/> from within deployment plans
> --------------------------------------------------------------------------
>
>                 Key: GERONIMO-3954
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3954
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>            Reporter: Janko Heilgeist
>            Assignee: David Jencks
>
> The provider or assembler of an JavaEE application can define environment entries inside the standard deployment descriptor files like ejb-jar.xml or web.xml with
> {code:xml}
> <env-entry>
>     <description>Some crucial variable!</description>
>     <env-entry-name>someVariable</env-entry-name>
>     <env-entry-type>java.lang.String</env-entry-type>
>     <!--env-entry-value>content of string</env-entry-value-->
> </env-entry>
> {code}
> Currently, the deployer of this application needs to modify the standard deployment descriptor to set the environment entry to a value. This is a problem, if e.g. the archive containing the descriptor file was signed by the provider and is supposed to be used unmodified. It would be a major improvement, if the Geronimo deployment plans would allow setting or overriding the values of these entries.
> This seems to have been the case in previous versions of Geronimo. On August 24th, 2003 the schema incubator-geronimo/modules/core/src/schema/geronimo-ejb-jar.xsd contained the following elements:
> {code:xml}
> [...]
> <xsd:element name="env-entry">
>   <xsd:annotation>
>     <xsd:documentation>
>       Configuration for an environment entry.  Normally an env-entry
>       is fully configured by the assembler in the standard ejb-jar.xml
>       deployment descriptor.  However, the deployer can specify a
>       value here if there was no value specified in ejb-jar.xml, or
>       if the deployer wants to override the value specified there.
>     </xsd:documentation>
>   </xsd:annotation>
>   <xsd:complexType>
>     <xsd:sequence>
>       <xsd:element ref="env-entry-name" minOccurs="1" maxOccurs="1"/>
>       <xsd:element ref="env-entry-value" minOccurs="1" maxOccurs="1"/>
>     </xsd:sequence>
>   </xsd:complexType>
> </xsd:element>
> [...]
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.