[jboss-jira] [JBoss JIRA] Updated: (AS7-1876) Field type resolution in @Resource doesn't occur (<env-entry-type> in ejb-jar.xml is required)

[jaikiran pai (JIRA)]

     [ https://issues.jboss.org/browse/AS7-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jaikiran pai updated AS7-1876:
------------------------------

           Assignee: Stuart Douglas  (was: David Lloyd)
    Forum Reference: http://community.jboss.org/message/627553  (was: http://community.jboss.org/message/627553)


> Field type resolution in @Resource doesn't occur (<env-entry-type> in ejb-jar.xml is required)
> ----------------------------------------------------------------------------------------------
>
>                 Key: AS7-1876
>                 URL: https://issues.jboss.org/browse/AS7-1876
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EE
>    Affects Versions: 7.0.1.Final
>         Environment: GNU/Linux Ubuntu 11.04 x86
>            Reporter: Pedro Kowalski
>            Assignee: Stuart Douglas
>
> While using @Resource on a field in EJB and defining it's value in ejb-jar.xml, the field type doesn't seem to be automatically resolved. It must be explicitly defined using <env-entry-type>.
> I attach exemplary application (+ sources) here: 
> http://community.jboss.org/servlet/JiveServlet/download/627566-41282/ENVTestAS7.jar
> The deployment will fail if the following line is commented:
> <env-entry-type>java.lang.String</env-entry-type>
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Could not determine type for <env-entry> java:comp/env/myEntry please specify the <env-entry-type>.
> After uncommenting it, the deployment runs fine.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira