I'm working on ARQ-593 at the moment, and there are few things that worry me. My experimental work for the bug fix is in one of the branches in my fork. What worries me is that although a ProtocolArchiveProcessor was written to relocate the glassfish-resources.xml, there are cases where @Resource injection would fail in tests.
For instance, if a developer were to
then, resource injection in a JUnit TestCase would fail, as the protocol unit typically tends to be a WAR. The EJB module is packaged within the WAR as a library in WEB-INF\lib, thus causing the container to ignore the resource mappings in the vendor descriptors. Eventually, a web-module specific deployment descriptor (glassfish-web.xml in this case) with the same mapping is required to make resource injection work.
This is not desirable from the point of view of testing EJBs, as a developer must now know
|Retrieving data ...|