Hi,
I've just faced a problem with endpoints as EJBs included in separate module in EAR application. So in my case I'm creating custom subclass of javax.ws.rs.core.Application with all classes defined in there. Some of the classes are EJBs existing in the other module. Unfortunatelly Jersey is trying to lookup for EJB using java:module context, which fails. Just wonder is this intentional or is it kind of issue? In JAX-RS spec v.1.1 says: "In a product that also supports EJB, an implementation MUST support use of stateless and singleton session beans as root resource classes, providers and Application subclasses." Nothing is said how beans should be packaged in an Enterprise Application.
Regards
JL