[
https://issues.apache.org/jira/browse/OPENEJB-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943068#comment-13943068
]
David Blevins commented on OPENEJB-2083:
----------------------------------------
There seems to be a possible compromise here.
Lou, the short story here is that we support things like @Inject on JAX-RS
services without the need for @ManagedBean.
Romain, how about we simply check for the existence of @ManagedBean on an @Path
(JAX-RS) component and simply ignore the @ManagedBean annotation. Seems we
could do that in the AnnotationDeployer.
> Jax-RS Resource annotated with @ManagedBean
> -------------------------------------------
>
> Key: OPENEJB-2083
> URL: https://issues.apache.org/jira/browse/OPENEJB-2083
> Project: OpenEJB
> Issue Type: Bug
> Components: tomee
> Environment: Windows 7. TomEE JAXRS 1.6.0
> Reporter: Lou Aloia
>
> JAX-RS resource annotated with @ManagedBean throws the following exception
> when attempting to invoke a method on the resource:
> Caused by: org.apache.openejb.SystemException:
> java.lang.NullPointerException: Cannot obtain an instance of the stateful
> session bean with a null session id: Cannot obtain an instance of the
> stateful session bean with a null session id
> at
> org.apache.openejb.core.managed.ManagedContainer.obtainInstance(ManagedContainer.java:630)
> at
> org.apache.openejb.core.managed.ManagedContainer.businessMethod(ManagedContainer.java:586)
> ... 40 more
> The resource only has stateless session beans that are injected into it; no
> stateful session beans.
> The application works fine on TomEE JAX-RS 1.5.2.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
