You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2012/12/27 17:16:12 UTC

[jira] [Resolved] (CXF-4722) JAX-RS documentation incorrect about phase of interceptors

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

Sergey Beryozkin resolved CXF-4722.
-----------------------------------

    Resolution: Fixed
      Assignee: Sergey Beryozkin

Please see
https://cwiki.apache.org/confluence/display/CXF20DOC/JAX-RS+Filters

Thanks
                
> JAX-RS documentation incorrect about phase of interceptors
> ----------------------------------------------------------
>
>                 Key: CXF-4722
>                 URL: https://issues.apache.org/jira/browse/CXF-4722
>             Project: CXF
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Matthew Morrissette
>            Assignee: Sergey Beryozkin
>            Priority: Minor
>              Labels: documentation, interceptors, jax-rs', phase
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> On the page:
> http://cxf.apache.org/docs/jax-rs-filters.html
> In the section:
> Difference between JAX-RS filters and CXF interceptors
> It notes that the JAXRSInInterceptor is tied to the Phase.PRE_STREAM phase.  However this was changed in revision# 775241 in trunk on the 15th of May, 2009 to the Phase.UNMARSHAL phase with the comment:
> JAX-RS : moving JAXRSInInterceptor to Phase.UNMARSHAL, support for relative URIs in ResponseBuilder.location
> Which means for all version of JAX-RS v 2.2.2 or higher (2.2.2 was released shortly thereafter), it is in the UNMARSHAL phase and for previous versions, it's in the PRE_STREAM phase. 
> The JAXRSOutInterceptor is correctly listed as MARSHAL phase.
> This caused me hours of confusion when writing custom interceptors.

--
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