[
https://issues.apache.org/jira/browse/CAMEL-3694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997462#comment-12997462
]
Claus Ibsen commented on CAMEL-3694:
------------------------------------
There was also an issue in the CxfRsInvoker which I have fixed as well
> CxfConsumer creates Continuation even when Endpoint is configured as
> synchronous.
> ---------------------------------------------------------------------------------
>
> Key: CAMEL-3694
> URL: https://issues.apache.org/jira/browse/CAMEL-3694
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
> Affects Versions: 2.6.0
> Reporter: Arnoud Glimmerveen
> Assignee: Claus Ibsen
> Fix For: 2.7.0
>
> Attachments: CxfConsumer.java.patch
>
>
> I am trying to get the camel-example-cxf-tomcat example running in a Servlet
> 3.0 container (Tomcat 7 and GlassFish v3). The example does not work directly
> on these platforms, as they require the CXFServlet async-supported property
> to be set to true (due to CxfEndpoint by default wanting to use the async
> API).
> I expected that when I configure the CxfEndpoint to be synchronous, that I do
> not need to modify the async-supported property of CXFServlet in the web.xml.
> However the "Continuation" used for async invocation is created before the
> synchronous property of the CxfEndpoint is evaluated, effectively requiring
> the async-supported to be true anyway.
> If my assumption that setting synchronous property on the CxfEndpoint should
> be sufficient, I propose to modify CxfConsumer (that creates the
> Continuation) to ensure the synchronous property is evaluated before any
> Continuation is created.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
