Hi
I suggest you send an ICLA to Apache and help fix/improve the docs.
Apache depend on people contributing on the projects.
If you want X fixed on page Y, then please make it super easy for
others to fix/do. Eg post a link and have replace FROM to TO so ppl
can do it easily.
On Fri, Sep 20, 2
FYI, probably a better syntax to use for accessing properties that does
work is properties.foo. Might want to put that in the documentation for
OGNL. Similarly, request.headers.foo would work for request headers.
On Fri, Sep 20, 2013 at 9:49 AM, Dale King wrote:
> To be a little more concrete,
To be a little more concrete, according to the documentation you linked to,
the following route should log "def" every second:
from("timer:foo")
.setProperty("foo").constant("abcdef")
.setBody().ognl("property('foo').substring(3)")
.log("${body}");
Inst
The last 2 rows of the variables table shows ways that are supposed to get
properties by name, but I tried to use it and it throws an exception. The
RootObject passed to OGNL has getProperty methods, but OGNL will not match
up property(...) to getProperty() method. OGNL 4 can match property[name]
t
Can you post the link to where you found this "mistake". I cannot see
a problem at
http://camel.apache.org/ognl
On Fri, Sep 20, 2013 at 12:57 AM, Dale King wrote:
> In the documentation for the Camel OGNL component it shows the following
> syntax:
>
> property(name) Object the property by the giv
Hi
You can help improve the docs. See
http://camel.apache.org/contributing.html
On Fri, Sep 20, 2013 at 12:57 AM, Dale King wrote:
> In the documentation for the Camel OGNL component it shows the following
> syntax:
>
> property(name) Object the property by the given name property(name, type) th
In the documentation for the Camel OGNL component it shows the following
syntax:
property(name) Object the property by the given name property(name, type) the
property by the given name as the given type
This syntax does not actually work in camel and I do not see any tests that
tried to test that
