No, it is not a bug. Your ejb modules does not have any resource
references that are satisfied by jackrabbit rar. Your ejb seems to be
accessing jackrabbit jca rar classes directly using jackrabbit API
called JCRUtils and GlassFish has no idea that this dependency comes
from jackrabbit rar. Add @Resource to your ejb to a jackrabbit rar
supplied connection factory for the class loader to detect the dependency.
Sahoo
On Tuesday 20 December 2011 11:39 PM, Gustavo Henrique Orair wrote:
> I checked the j2EE6 specification for classloading behaviour.
> In section 8.3.2 - EJB Container Class Loading Requirements it states:
>
> "/Components in the EJB container must have access to the following
> classes and resources.
> (/...)
> /* The contents of all jar files included in each resource adapter
> archive (rar file) deployed separately to the application server, if
> that resource adapter is used to satisfy any resource references in
> the module.
> (...)"
>
> /So, the behaviour I found in Glassfish seems like not J2EE6 compliant.
>
> Should I file a bug?