Are they local EJBs or remote EJBs? I assume the latter. In that case,
just package the ejb interface classes in the client bundle and add a
DynamicImport-Package: * instruction in the client bundle. This is
required because when you look up a remote ejb, the naming lookup will
result in generation of some ejb proxy classes in the class loader of
the client bundle. Those proxy classes references glassfish
implementation specific classes which your bundle has no idea of at
development time.
Sahoo
On Thursday 22 December 2011 06:00 PM, forums_at_java.net wrote:
> Hi,
>
> The existing EJBs are not under our responsability.
>
> Moreover, they are already active in production for other purposes of the
> project and turning upside down their infrastructure would be too
> risky for
> our management to approve.
>
>
> --
>
> [Message sent by forum member 'elevy30']
>
> View Post: http://forums.java.net/node/875956
>
>