[
https://issues.apache.org/jira/browse/CAMEL-6403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-6403.
--------------------------------
Resolution: Fixed
Ideally the consumer should write its response in the async callback done
method, then there UoW is not done yet.
Though some of these http related components is a bit different and needed this
support.
Well spotted Gert.
> Add support for UnitOfWork per request
> --------------------------------------
>
> Key: CAMEL-6403
> URL: https://issues.apache.org/jira/browse/CAMEL-6403
> Project: Camel
> Issue Type: Improvement
> Components: camel-jetty
> Affects Versions: 2.11.0
> Reporter: Gert Vanthienen
> Assignee: Claus Ibsen
> Fix For: 2.12.0
>
>
> When using a {{camel-jetty}} endpoint, the {{UnitOfWork}} is not being
> managed by the servlet handling the request but by the Camel route that's
> being invoked.
> This means that some resources have already been removed/cleaned up when the
> servlet is writing the response, e.g. files for cached streams have already
> removed before the servlet gets a chance to read from them.
> It would be nice to have an option available to configure the servlet itself
> to handle the unit of work and mark it {{done}} after the HTTP response has
> been written. That way, the unit of work can be matched up with the actual
> HTTP request.
--
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
