[
https://issues.jboss.org/browse/AS7-1876?page=com.atlassian.jira.plugin.s...
]
Pedro Kowalski commented on AS7-1876:
-------------------------------------
Yeah, you mentioned the EjbRefProcessor, so I guess you already know that the ejb-ref is
also not able to figure out what EJB type it's referencing, so you need to specify
i.e. the <local> sub-element of <ejb-local-ref> element (as described in
forum's post).
Thanks in advance for looking at it!
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/ENVT...
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