This is an automated email from the ASF dual-hosted git repository. gnodet pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/camel.git
commit 3588e69fadc502b16085a3d334705a2b30e3c549 Author: Guillaume Nodet <[email protected]> AuthorDate: Wed May 22 20:08:28 2019 +0200 Indent comment to make it a multiline todo --- .../java/org/apache/camel/impl/engine/DefaultUnitOfWork.java | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/core/camel-base/src/main/java/org/apache/camel/impl/engine/DefaultUnitOfWork.java b/core/camel-base/src/main/java/org/apache/camel/impl/engine/DefaultUnitOfWork.java index 488f030..78a24f2 100644 --- a/core/camel-base/src/main/java/org/apache/camel/impl/engine/DefaultUnitOfWork.java +++ b/core/camel-base/src/main/java/org/apache/camel/impl/engine/DefaultUnitOfWork.java @@ -55,11 +55,11 @@ public class DefaultUnitOfWork implements UnitOfWork, Service { private static final Logger LOG = LoggerFactory.getLogger(DefaultUnitOfWork.class); // TODO: This implementation seems to have transformed itself into a to broad concern - // where unit of work is doing a bit more work than the transactional aspect that ties - // to its name. Maybe this implementation should be named ExchangeContext and we can - // introduce a simpler UnitOfWork concept. This would also allow us to refactor the - // SubUnitOfWork into a general parent/child unit of work concept. However this - // requires API changes and thus is best kept for Camel 3.0 + // where unit of work is doing a bit more work than the transactional aspect that ties + // to its name. Maybe this implementation should be named ExchangeContext and we can + // introduce a simpler UnitOfWork concept. This would also allow us to refactor the + // SubUnitOfWork into a general parent/child unit of work concept. However this + // requires API changes and thus is best kept for Camel 3.0 private UnitOfWork parent; private String id;
