On 03/22/2011 02:42 PM, Andrig Miller wrote:
> If OrderManagerEntities.jar is in the EAR's "lib"
directory (or the
> directory you have configured as such in application.xml) then the
> OrderManagerEJB.jar should be able to "see" it. If not then you'll
> need
> an explicit "Class-Path" reference to it from your EJB JAR.
No, my OrderManagerEntities.jar is not the EAR's "lib" directory, its at
the same level as the OrderManagerEJB.jar, and its listed as an EJB module in the
application.xml.
This seems broken to me.
As a rule, we are restricting visibility by default as much as the spec
allows (which may mean certain behaviors are different from AS 5/6). So
the question is really, is this contrary to spec? If so, it's a bug.
That's what we need to answer.
--
- DML