[
https://issues.apache.org/jira/browse/MEAR-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143106#comment-16143106
]
Karl Heinz Marbaise commented on MEAR-248:
------------------------------------------
The first thing is your example is not correct cause it must look like this(see
docs):
{code:xml}
<configuration>
<env-entries>
<env-entry>
<env-entry-name>ExampleString</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<lookup-name>java:global/Example</lookup-name>
</env-entry>
</env-entries>
</configuration>
{code}
Apart from that yes you are right {{lookup-name}} is not supported yet. This
can be achieved easily.
> Support lookup-name in env-entry section
> ----------------------------------------
>
> Key: MEAR-248
> URL: https://issues.apache.org/jira/browse/MEAR-248
> Project: Maven Ear Plugin
> Issue Type: New Feature
> Affects Versions: 2.10.1
> Reporter: Thomas Seidel
> Fix For: 3.0.0
>
>
> Add support for lookup-name tag in env-entry section to support JNDI lookup.
> Currently, this tag is ignored in generated application.xml.
> Example:
> The pom.xml snippet
> {code:xml}
> <configuration>
> <env-entries>
> <env-entry-name>ExampleString</env-entry-name>
> <env-entry-type>java.lang.String</env-entry-type>
> <lookup-name>java:global/Example</lookup-name>
> </env-entries>
> </configuration>
> {code}
> should generate application.xml with
> {code:xml}
> <env-entry-name>ExampleString</env-entry-name>
> <env-entry-type>java.lang.String</env-entry-type>
> <lookup-name>java:global/Example</lookup-name>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
