Return-Path: 
 <users-return-43009-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-users-archive@www.apache.org
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id BDE8F10AD4
	for <apmail-camel-users-archive@www.apache.org>;
 Fri, 20 Sep 2013 05:55:41 +0000 (UTC)
Received: (qmail 51123 invoked by uid 500); 20 Sep 2013 05:55:33 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 51072 invoked by uid 500); 20 Sep 2013 05:55:29 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 51060 invoked by uid 99); 20 Sep 2013 05:55:26 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Sep 2013 05:55:26 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.223.172 as permitted sender)
Received: from [209.85.223.172] (HELO mail-ie0-f172.google.com)
 (209.85.223.172)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Sep 2013 05:55:20 +0000
Received: by mail-ie0-f172.google.com with SMTP id x13so17460694ief.17
        for <users@camel.apache.org>; Thu, 19 Sep 2013 22:54:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        bh=9w1snV31cqmtZIWLpG1YLx8uOQ4zWwF6Kcz6EF7FDFs=;
        b=G/DAPBGVlGCWDaU0WFrSVDVQT1C1YCxJBHEnL7PNLYuNm6B2DYBWg8jnd5Pzk5mjh9
         DezTo7KoNPL73BLKmeQsqVIy4VvHiJwAO/f2bXOqHR8p38f8DmUfkuPZGvF33uFYwUTo
         0C47ej/LDk1H+EjIx14zxXtqpaSQ3ju2DaUUFet7Fh3gTbUYKEsXdv5R8Fqw81JZD9Gb
         b41iVzTX2bGVnXxBuGD7QbcuR6NG9WJ/OtnmXWL4e8pRg6dma6pRRrHsHHrUBVRlsCZM
         BHBaLOHaeR2QZsM4aSik/OQFPHhobz3+rYM7GuoJb0bRTHG/6LxIxO4d9wmMebUtVKpm
         z0BA==
X-Received: by 10.50.136.200 with SMTP id qc8mr1315200igb.52.1379656499250;
 Thu, 19 Sep 2013 22:54:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.19.4 with HTTP; Thu, 19 Sep 2013 22:54:39 -0700 (PDT)
In-Reply-To: 
 <CA+14yuLKcxHBP61WKdDfd1+a61q-JHcKYRi7v4QbGw2VAjxwGg@mail.gmail.com>
References: 
 <CA+14yuJJcRqiUwe7p7RwF1PkuybSWMjk6vqWMLj1bKNvD+8kFw@mail.gmail.com>
 <CAGB5yN=_+pm7UriyVqk+Xw4fGz0Jdxjf3xh6QJdkzKhrD16hoA@mail.gmail.com>
 <CA+14yu+5Xifwio9UiCi=TxyE6ELFbExOKTvR2a9F=eB7=ugxVA@mail.gmail.com>
 <CA+14yuLKcxHBP61WKdDfd1+a61q-JHcKYRi7v4QbGw2VAjxwGg@mail.gmail.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Fri, 20 Sep 2013 07:54:39 +0200
Message-ID: 
 <CAGB5yN=xiLwwEgSxNYO1DogLkXXS6NmWsMQtEwirvsjitKTJXw@mail.gmail.com>
Subject: Re: Simple way to do some elementary bean operations
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

Hi

You can use the language component, and set transform=false
http://camel.apache.org/language

Though the idea of having a <script> in the DSL seems good. Though we
are often a bit careful to add to the DSL to not make it too big.


On Thu, Sep 19, 2013 at 8:23 PM, Dale King <dalewking@gmail.com> wrote:
> Thinking about this some more the real issue is not so much direct support
> for setting properties or invoking arbitrary methods because we have things
> like OGNL which can do that work for us. For example, the OGNL expression:
>
>    request.body.someProperty = request.headers.foo
>
> would do the trick for setting a property without resorting to Java.
>
> The real problem is that there is no way to just invoke a script like this
> without requiring you to do something with the result (store it in the
> body, a property, a header, use the value as a filter, etc.) We need a way
> to just say invoke this expression which could be in OGNL, Groovy,
> Javascript, etc. without being forced to do something with the result.
>
> Looking at the code there is the EvaluateExpressionProcessor which would be
> perfect for this. It evaluates an expression and stores the result in a
> property "CamelEvaluateExpressionResult". All we need is DSL to create an
> instance of this.
>
> So in Java DSL it would be something like:
>
>     .eval().ognl("request.body.someProperty = request.headers.foo")
>
> In Spring DSL it would be something like:
>
>     <eval><ognl>request.body.someProperty =
> request.headers.foo</ognl></eval>
>
> The workaround for now is to do the equivalent:
>
>     .setProperty("dummy").ognl("request.body.someProperty =
> request.headers.foo")
>
>
> On Tue, Sep 3, 2013 at 2:09 PM, Dale King <dalewking@gmail.com> wrote:
>
>> Yeah, LIKE I SAID, I know I can break out to a bean or a processor, but
>> that is such a heavyweight solution to do something so simple that really
>> should be built into Camel. You have to create a class, come up with some
>> meaningful name of the class, repeat that name a couple of times if using a
>> Spring DSL, etc.
>>
>> Let's say we do it with anonymous classes in a Java DSL:
>>
>>   process(new Processor()
>>   {
>>         @Override
>>          public void process(Exchange exchange) throws Exception
>>          {
>>                exchange.getIn().getBody(MyBodyType.class)
>>
>> .setSomeProperty(exchange.getIn().getHeader("foo", SomeType.class);
>>          }
>>   })
>>
>> Or perhaps better as a bean:
>>
>>   bean( new Object()
>>   {
>>       public void set( @Body MyBodyType body, @Header("foo") value)
>>       {
>>           body.setSomeProperty(value);
>>       }
>>   }
>>
>> I personally would rather replace any of those with something more like
>> this in DSL:
>>
>>   body().set("someProperty", header("foo"))
>>
>> This is much more obvious what is happening when looking at the route.
>>
>>
>>
>> On Tue, Sep 3, 2013 at 1:51 PM, Claus Ibsen <claus.ibsen@gmail.com> wrote:
>>
>>> On Tue, Sep 3, 2013 at 5:51 PM, Dale King <dalewking@gmail.com> wrote:
>>> > Through simple and OGNL we have nice easy ways to read the properties of
>>> > beans in the body, headers, or properties. But what I cannot find is an
>>> > easy way to invoke a setter on a bean property, but perhaps I am missing
>>> > something.
>>> >
>>> > I can certainly create a bean or processor to invoke the setter, but it
>>> > seems to me that if I am forced to do it for something as simple as
>>> setting
>>> > a property then something is missing in Camel. I try to do as much as
>>> > possible in Camel.
>>> >
>>> > I can certainly use another language like javascript, groovy, or el to
>>> do
>>> > it, but once again bringing in a whole new language seems like overkill
>>> > just to set a property.
>>> >
>>> > So 3 operations that i don't see an easy way to do in Camel without
>>> > resorting to these heavyweight solutions are:
>>> >
>>> >  - Set a bean property
>>> >  - More generally, you should be able to invoke any method on a bean
>>> > including with parameters
>>> >  - Create a new instance of a bean (possibly with parameters)
>>> >
>>> > Correct me if I am wrong and there is a simple way to do these.
>>> >
>>>
>>> Well there is something called Java programming language, where you
>>> can do all that ;)
>>>
>>> > --
>>> > Dale King
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> Red Hat, Inc.
>>> Email: cibsen@redhat.com
>>> Twitter: davsclaus
>>> Blog: http://davsclaus.com
>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>
>>
>>
>>
>> --
>> Dale King
>>
>
>
>
> --
> Dale King



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen