[
https://issues.apache.org/activemq/browse/CAMEL-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62193#action_62193
]
Willem Jiang commented on CAMEL-3169:
-------------------------------------
Hi Martin,
In Jetty6, the continuation suspend is implemented by throwing a runtime
exception, so you need to set up the async call back before calling the
continuation suspend.
In Jetty7, you can set up the async call back after calling the suspend method
of continuation, and patch of CAMEL-2986 works perfect for you.
Because the continuation of CXF 2.2.x is based on thrown a runtime exception, I
can't change the code as you do in CAMEL-2986.
I already did some work in CXF-2982[1], and I will updated the camel-cxf code
once upgrade CXF version to 2.3.0.
[1]https://issues.apache.org/jira/browse/CXF-2982
Willem
> Add continuation synchronize block to avoid the CamelAsync API return earlier
> then the interceptor chain is suspend
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-3169
> URL: https://issues.apache.org/activemq/browse/CAMEL-3169
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-cxf
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 2.5.0
>
>
> As the CamelAsyncProcess always takes some time to do it job, we barely hit
> the upper situation, but it still has chance to hit this situation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
