You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Yuri Schimke (JIRA)" <ji...@apache.org> on 2009/08/12 23:51:36 UTC
[jira] Created: (CAMEL-1909) cxfrs improvements
cxfrs improvements
------------------
Key: CAMEL-1909
URL: https://issues.apache.org/activemq/browse/CAMEL-1909
Project: Apache Camel
Issue Type: Improvement
Components: camel-cxf
Affects Versions: 2.0-M3
Reporter: Yuri Schimke
http://camel.apache.org/cxfrs.html
My main question with this component is why it forces a concrete implementation of the resource class. My implementation for a JAXRS annotated interface, is just to use a ProducerTemplate to call back into camel. Therefore it would be nice if I could skip that concrete implementation and just pass through the request either as a BeanInvocation, or for a method with a single parameter pass that parameter as the body.
For the functionality the current cxfrs component provides it seems much easier to expose my current class using the cxf functionality and then call into camel.
One minor other issues on the page above, the following example uses cxf instead of cxfrs, and also needs to refer to resourceClasses instead of ResourceClass
cxf:bean:cxfEndpoint?ResourceClass=org.apache.camel.rs.Example
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CAMEL-1909) cxfrs improvements
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CAMEL-1909:
-----------------------------------
Assignee: Willem Jiang (was: William Tam)
> cxfrs improvements
> ------------------
>
> Key: CAMEL-1909
> URL: https://issues.apache.org/activemq/browse/CAMEL-1909
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-cxf
> Affects Versions: 2.0-M3
> Reporter: Yuri Schimke
> Assignee: Willem Jiang
> Priority: Minor
> Fix For: 2.2.0
>
>
> http://camel.apache.org/cxfrs.html
> My main question with this component is why it forces a concrete implementation of the resource class. My implementation for a JAXRS annotated interface, is just to use a ProducerTemplate to call back into camel. Therefore it would be nice if I could skip that concrete implementation and just pass through the request either as a BeanInvocation, or for a method with a single parameter pass that parameter as the body.
> For the functionality the current cxfrs component provides it seems much easier to expose my current class using the cxf functionality and then call into camel.
> One minor other issues on the page above, the following example uses cxf instead of cxfrs, and also needs to refer to resourceClasses instead of ResourceClass
> cxf:bean:cxfEndpoint?ResourceClass=org.apache.camel.rs.Example
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CAMEL-1909) cxfrs improvements
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-1909:
----------------------------------
Assignee: William Tam
William can you take a look at this?
> cxfrs improvements
> ------------------
>
> Key: CAMEL-1909
> URL: https://issues.apache.org/activemq/browse/CAMEL-1909
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-cxf
> Affects Versions: 2.0-M3
> Reporter: Yuri Schimke
> Assignee: William Tam
>
> http://camel.apache.org/cxfrs.html
> My main question with this component is why it forces a concrete implementation of the resource class. My implementation for a JAXRS annotated interface, is just to use a ProducerTemplate to call back into camel. Therefore it would be nice if I could skip that concrete implementation and just pass through the request either as a BeanInvocation, or for a method with a single parameter pass that parameter as the body.
> For the functionality the current cxfrs component provides it seems much easier to expose my current class using the cxf functionality and then call into camel.
> One minor other issues on the page above, the following example uses cxf instead of cxfrs, and also needs to refer to resourceClasses instead of ResourceClass
> cxf:bean:cxfEndpoint?ResourceClass=org.apache.camel.rs.Example
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-1909) cxfrs improvements
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-1909:
-------------------------------
Priority: Minor (was: Major)
Fix Version/s: 2.2.0
> cxfrs improvements
> ------------------
>
> Key: CAMEL-1909
> URL: https://issues.apache.org/activemq/browse/CAMEL-1909
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-cxf
> Affects Versions: 2.0-M3
> Reporter: Yuri Schimke
> Assignee: William Tam
> Priority: Minor
> Fix For: 2.2.0
>
>
> http://camel.apache.org/cxfrs.html
> My main question with this component is why it forces a concrete implementation of the resource class. My implementation for a JAXRS annotated interface, is just to use a ProducerTemplate to call back into camel. Therefore it would be nice if I could skip that concrete implementation and just pass through the request either as a BeanInvocation, or for a method with a single parameter pass that parameter as the body.
> For the functionality the current cxfrs component provides it seems much easier to expose my current class using the cxf functionality and then call into camel.
> One minor other issues on the page above, the following example uses cxf instead of cxfrs, and also needs to refer to resourceClasses instead of ResourceClass
> cxf:bean:cxfEndpoint?ResourceClass=org.apache.camel.rs.Example
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1909) cxfrs improvements
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-1909.
---------------------------------
Resolution: Fixed
Thanks for pointing that out, I already updated the wiki page for it.
> cxfrs improvements
> ------------------
>
> Key: CAMEL-1909
> URL: https://issues.apache.org/activemq/browse/CAMEL-1909
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-cxf
> Affects Versions: 2.0-M3
> Reporter: Yuri Schimke
> Assignee: Willem Jiang
> Priority: Minor
> Fix For: 2.2.0
>
>
> http://camel.apache.org/cxfrs.html
> My main question with this component is why it forces a concrete implementation of the resource class. My implementation for a JAXRS annotated interface, is just to use a ProducerTemplate to call back into camel. Therefore it would be nice if I could skip that concrete implementation and just pass through the request either as a BeanInvocation, or for a method with a single parameter pass that parameter as the body.
> For the functionality the current cxfrs component provides it seems much easier to expose my current class using the cxf functionality and then call into camel.
> One minor other issues on the page above, the following example uses cxf instead of cxfrs, and also needs to refer to resourceClasses instead of ResourceClass
> cxf:bean:cxfEndpoint?ResourceClass=org.apache.camel.rs.Example
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.