geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Assigned: (GERONIMO-3954) Allow overriding the value of an <env-entry/> from within deployment plans
Date Thu, 26 Mar 2009 09:23:58 GMT


David Jencks reassigned GERONIMO-3954:

    Assignee: David Jencks

> Allow overriding the value of an <env-entry/> from within deployment plans
> --------------------------------------------------------------------------
>                 Key: GERONIMO-3954
>                 URL:
>             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
> {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.

View raw message