[
https://issues.apache.org/jira/browse/OPENEJB-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943088#comment-13943088
]
David Blevins commented on OPENEJB-2083:
----------------------------------------
That whole @Stateful similarity was an interpretation we made and no one else
did. We support a lot of annotations on @ManagedBean that no one else does.
So just as equally unportable. @ManagedBean is effectively dead now -- no work
was done on it in Java EE 7.
@ManagedBean created more of a mess for Java EE than actual functionality.
IMO, the best thing we can do as vendors to clean up that mess is do our best
to decrease the incompatibilities it created.
When we see @ManagedBean and @Path together, we can ignore it and then log a
statement (just one for the whole application) that the @ManagedBean was
ignored.
> 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)
