Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-user@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of james.strachan@gmail.com
 designates 209.85.217.15 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=P5qDEbWU4SDKm9bAbMGPpjMG24NfdXGWx8CvISNx0UUD5OBPBGfiy5VZpZHr0dt3O/
         LcrOJ1nIriZHoU8iA7ccrdJ3eZ1o0iZaSBLy6zLcRN4eDqItILyzae3mz3B0Mil+F+oR
         jTXfTVBvZbm6szWQ3gey+q4M0bUC0KepVvGZA=
Message-ID: <ec6e67fd0809160331s4f5f6fd5qdbb2d10d408e22e8@mail.gmail.com>
Date: Tue, 16 Sep 2008 11:31:41 +0100
From: "James Strachan" <james.strachan@gmail.com>
To: camel-user@activemq.apache.org
Subject: Re: Custom log messages
In-Reply-To: <19508601.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <19508418.post@talk.nabble.com>
	 <4C1FB9C00D24A140906239533638C4D20551C48C@EXVS04.exserver.dk>
	 <19508601.post@talk.nabble.com>

2008/9/16 raulvk.soa <raulvk.soa@gmail.com>:
>
> Hi Claus,
>
> My requirement is a bit different... I need to print human-readable messages
> such as "Validating against XML Schema...", "Validation OK", "Validation
> ERROR", etc... Therefore, I need to be able to specify the message that
> should be printed out when I am building the route.
>
> Don't know if I have expressed myself clearly...
>
> Is there any functionality in Camel that will allow me to do send custom log
> messages to the Log component?

You could use a templating engine to transform the message into a
human readable format first, before routing it to the log component.

See...
http://activemq.apache.org/camel/templating.html

for example

from("...").
  to("velocity:scripts/Validating.vm").
  to("log:Validating");

then your Validating.vm script could generate text extracting some
headers or payload from the message etc.

Maybe if the logging information is simpler; we could just use normal
expressions?

e.g. using the EL as a kinda templating engine

from("...").
        setBody().el("Validating ${in.header.foo} blah").
        to("log:Validating");

Templating engines come into their own when you are composing a large
page of text such as an email with embedded values; if its a single
line of text for a log message or SMS or something then using EL or
XPath or something might be simpler as you can inline the expression
inside your route.

-- 
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://open.iona.com