Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
MIME-Version: 1.0
Date: Fri, 24 Jul 2015 16:13:56 -0400
Message-ID: 
 <CA+du6=-dtaqD_EAmd80XWUtopcYGP8ORh9L31Gs1HHZcMX1gmQ@mail.gmail.com>
Subject: Placing and referencing DTO via exchange properties
From: Craig Taylor <ctalkobt@ctalkobt.net>
To: users <users@camel.apache.org>
Content-Type: multipart/alternative; boundary=001a113dfe36c47e7c051ba4a4a0

--001a113dfe36c47e7c051ba4a4a0
Content-Type: text/plain; charset=UTF-8

I'm attempting the following route given a TestDTO implemented which has a
constructor / getter / setter for a name property:


                from ("direct:testDTO")
                    .setProperty("testDTO",bean(testDTO))
                    .to("direct:testDTO2");

                from ("direct:testDTO2")
                    .log(LoggingLevel.ERROR, "testDTO property is : ${
property.testDTO.name}")
                    ;

The logging output yields only

[                          main] route2                         ERROR
testDTO property is :

I've tried a number of other types of placement such as constant() etc in
place of bean with the same results.

Thoughts / Suggestions?

(I'm really trying to avoid placing the individual elements of the DTO on
the exchange as there will be a large number of them and the existing /
intended business services are already focused around usage of a DTO
reference.  I'm using a property rather than a header due the fact that the
body itself will undergo a number of different changes).
-- 
-------------------------------------------
Craig Taylor
ctalkobt@ctalkobt.net

--001a113dfe36c47e7c051ba4a4a0--