Hi
Thanks I logged a ticket
https://issues.apache.org/jira/browse/CAMEL-9870
On Thu, Apr 14, 2016 at 10:00 PM, Mario Balaban wrote:
> I am using version 2.16.1. The example is something like this:
>
>
>
> and the the java bean method is:
>
> public void addNote(String
I am using version 2.16.1. The example is something like this:
and the the java bean method is:
public void addNote(String invoice, String note){
...}
In this case the binding expression assigns the result of Invoice.toString
method to the first argument and null to the second even if
On Thu, Apr 14, 2016 at 10:23 AM, Mario Balaban wrote:
> Hello, I also have been passing a couple of hours trying to debug a missing
> parenthesis from a bean binding expression. It would be nice if the parser
> threw an exception in case of missing close parenthesis.
Hello, I also have been passing a couple of hours trying to debug a missing
parenthesis from a bean binding expression. It would be nice if the parser
threw an exception in case of missing close parenthesis. Thanks!
--
View this message in context:
Ok, thanks Claus.
Would you recommend trying 2.15.3 or 2.16? Is 2.15.3 the latest stable?
--
View this message in context:
http://camel.465427.n5.nabble.com/Apache-Camel-bean-parameter-binding-issue-with-Spring-DSL-tp5772200p5772294.html
Sent from the Camel - Users mailing list archive at
Hi
I am sorry to say it but you may try a newer release to see if it works there.
I could not reproduce any issue on lastest code. And mind that
${exchange} has just only been added to simple language in 2.16
release.
On Mon, Oct 5, 2015 at 2:47 PM, wheli wrote:
>
Sure...
public String extractDocumentRootOid(Exchange exchange) throws Exception
public Organization getOrganizationByOid(Exchange exchange, String oid)
throws InterchangeException
(Organization is a custom java object)
public String extractStyleSheetAttributeFromOrganization(Exchange exchange,
I'd rather not be pigeon-holed with the header namemeaning, I'd like to
make it so that the creator of any route can name the header whatever they
want, and use this method, without having any knowledge of the method
parameters (having to go look at the java components).
--
View this
Hi
Yeah you can try latest 2.13.x in case you consider upgraded on
existing release branch.
But 2.15.3 is the latest stable release. And 2.16.0 is being built
this week and hopefully GA next week.
On Mon, Oct 5, 2015 at 3:02 PM, wheli wrote:
> Ok, thanks Claus.
>
>
I upgraded and it made no difference, but then I noticed that I was missing a
closing parenthesis on my "transformBodyUsingStyleSheet" method. I fixed
this and it resolved the issue. Sorry for not seeing that, but i am all set
now. Thanks!
--
View this message in context:
On Mon, Oct 5, 2015 at 4:13 PM, wheli wrote:
> I upgraded and it made no difference, but then I noticed that I was missing a
> closing parenthesis on my "transformBodyUsingStyleSheet" method. I fixed
> this and it resolved the issue. Sorry for not seeing that, but i am
Hi,
You may try one of the below two approaches:
1. Redefine your method signature and use the Bean annotations.
public void transformBodyUsingStyleSheet(Exchange exchange,
@Header("organizationStyleSheet") String styleSheet)
{
..
}
2. If the above didn't work, modify the bean delcaration in
Can you should the method signature for those methods. Also if they
are void or return a value. And what version of Camel do you use?
On Fri, Oct 2, 2015 at 10:18 PM, wheli wrote:
> I am running into a strange issue with Apache Camel and Spring DSL. Here is
> an
13 matches
Mail list logo