On Oct 21, 2009, at 1:42 PM, glassfish_at_javadesktop.org wrote:
> [*] If you are using the latest GF v3 and you annotate your resource
> class with @ManagedBean you will no longer require the custom EJB
> provider.
>
>
> much better.. but then I get back to my original problem in the
> other thread, I am trying without success to inject the EJB in the
> ManagedBean :)
>
> I have in the same EAR a war file with the Jersey Service and other
> war file with a JSF2 application.. the jersey Service always worked
> with the EjbProvider, I will try on the evening to use the trick
> with the managedbean.. let's see.. once I cross this issue I will
> finally unveil the full powers of my EAR application :)
> [Message sent by forum member 'felipegaucho' (fgaucho_at_gmail.com)]
You might want to try placing you @ManagedBean annotated root resource
classes in the war.
@ManagedBean
@Path("/root")
public class MyResourceClass {
}
Paul.