[jira] [Resolved] (CAMEL-8383) CXFRS Consumer processors should be able to use JAX-RS contexts

["Claus Ibsen (JIRA)" <ji...@apache.org>]

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

Claus Ibsen resolved CAMEL-8383.
--------------------------------
    Resolution: Fixed
      Assignee: Claus Ibsen

Thanks for the patch.

Do you mind adding some documentation to
http://camel.apache.org/cxfrs

about this new option?

> CXFRS Consumer processors should be able to use JAX-RS contexts
> ---------------------------------------------------------------
>
>                 Key: CAMEL-8383
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8383
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-cxf
>            Reporter: Sergey Beryozkin
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.15.0
>
>         Attachments: patch8383.txt
>
>
> CXFRS consumer processors should be able to use JAX-RS Contexts, for example, instead of 
> {code:java}
> String path = exchange.getIn().getHeader(Exchange.HTTP_PATH, String.class);
> if (path.equals("/customers")) {
> //...
> } 
> {code}
> do something like
> {code:java}
> javax.ws.rs.core.UriInfo ui = exchange.getProperty(UriInfo.class.getName(), UriInfo.class);
> if (ui.getPath().equals("/customers")) {
> //...
> } 
> {code}
> This will make the processor code more JAX-RS friendly. Besides UriInfo, Request, HttpHeaders and other JAX-RS contexts offer a lot of utility methods for simplifying managing an HTTP request



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)