[jboss-jira] [JBoss JIRA] Commented: (AS7-1112) EJB annotation processing DUP fails to find annotations from classes belonging to jars in .ear/lib
[
https://issues.jboss.org/browse/AS7-1112?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-1112:
-----------------------------------
The issue here is that the EJB3 annotation processors end up using *only* the
CompositeIndex of the ejb.jar DU. These processors should also be using the CompositeIndex
of the parent .ear. Overall, this is going to require some refactoring on how the EJB3
annotation processing DUPs are implemented.
EJB annotation processing DUP fails to find annotations from classes
belonging to jars in .ear/lib
--------------------------------------------------------------------------------------------------
Key: AS7-1112
URL: https://issues.jboss.org/browse/AS7-1112
Project: Application Server 7
Issue Type: Bug
Components: EJB
Environment: AS7 upstream (June 24 2011)
Reporter: jaikiran pai
Assignee: jaikiran pai
Consider the following deployment:
{code}
.ear
|
|--- lib/lib.jar
|
|--- ejb.jar
{code}
If ejb.jar contains:
{code}
@Stateless
public class MyBean implements SomeInterface {
}
{code}
and the lib/lib.jar contains the interface:
{code}
@Remote
public interface SomeInterface {
...
}
{code}
then the BusinessViewAnnotationProcessor complains about missing index for the
SomeInterface class:
{code}
09:05:28,739 WARN
[org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor] (MSC service
thread 1-2) Could not read annotations on EJB interface blah.blah.SomeInterface
{code}
Please see the referenced forum thread for the details.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira