You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Forrest Xia (JIRA)" <ji...@apache.org> on 2013/05/27 14:35:26 UTC

[jira] [Updated] (GERONIMO-6122) Support Stateless and Singleton EJB as JAX-RS root resource classes, providers and Application subclasses

     [ https://issues.apache.org/jira/browse/GERONIMO-6122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Forrest Xia updated GERONIMO-6122:
----------------------------------

    Fix Version/s:     (was: 3.0.1)
                   3.0.2
    
> Support Stateless and Singleton EJB as JAX-RS root resource classes, providers and Application subclasses
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-6122
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6122
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: javaee6
>    Affects Versions: 3.0.0
>            Reporter: viola.lu
>            Assignee: Ivan
>            Priority: Minor
>             Fix For: 3.0.2
>
>
> From JAX-RS spec 1.1
> 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. JAX-RS annotations
> MAY be applied to a bean's local interface or directly to a no-interface bean. If an Exception-
> Mapper for a EJBException or subclass is not included with an application then exceptions thrown
> by an EJB resource class or provider method MUST be treated as EJB application exceptions: the
> embedded cause of the EJBException MUST be unwrapped and processed as described in section
> 3.3.4.
> Now geronimo recognize javax.ws.rs.URIinfo as EJB resource in a stateless EJB, so failed to get Uriinfo
> Run Restfulorder samples can give more details.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira