[
https://issues.apache.org/activemq/browse/CAMEL-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-2109:
-------------------------------
Description:
When building a route like this:
{code}
....
public void configure() {
from("jms:fileIn?transacted=true")
.onException(UnmarshalException.class)
.handled(true)
.bean(FileProcessExceptionBean.class,"handleException")
.end()
.id("fileMapping")
.transacted()
.process(new FileProcessor())
.to("jms:fileOut");
}
{code}
the id is not set. When the onException-section is removed, the id is set
correctly
was:
When building a route like this:
....
public void configure() {
from("jms:fileIn?transacted=true")
.onException(UnmarshalException.class)
.handled(true)
.bean(FileProcessExceptionBean.class,"handleException")
.end()
.id("fileMapping")
.transacted()
.process(new FileProcessor())
.to("jms:fileOut");
}
the id is not set. When the onException-section is removed, the id is set
correctly
> ID of route is not set when onException is used
> -----------------------------------------------
>
> Key: CAMEL-2109
> URL: https://issues.apache.org/activemq/browse/CAMEL-2109
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 2.1.0
> Environment: Apache Camel 2.1-SNAPSHOT (build 20091022) , Java 1.6.0,
> Linux
> Reporter: Patrick Klippel
>
> When building a route like this:
> {code}
> ....
> public void configure() {
> from("jms:fileIn?transacted=true")
> .onException(UnmarshalException.class)
> .handled(true)
> .bean(FileProcessExceptionBean.class,"handleException")
> .end()
> .id("fileMapping")
> .transacted()
> .process(new FileProcessor())
> .to("jms:fileOut");
> }
> {code}
> the id is not set. When the onException-section is removed, the id is set
> correctly
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
