|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I think this scenario should result either in unsatisfied or ambiguous dependency. It depends on the visibility configuration. In portable applications by default EJB jars do not see WARs and vice versa (see also "EE.8.3 Class Loading Requirements"). So if we do not specify dependencies in manifest files we get unsatisfied dependency. And if we follow all the visibility requirements (EJB sees A and B, A and B see EJB) we get ambiguous dependency.