Yes I have been using jconsole to try to piece together what the
getDescription() used to provide but have not found all the answers.
What the route.getDescription() used to provide in the 'processor' part was
the 'to' route. E.g. where is the data going next and that is what the app
really
You can get the processors of the route in the processors tree. They
have attribute which route they are part of, and a order num attribute
that indicate in what position in the route they are from.
You can also get the route overview by invoking the dump route as xml
operations on the route or
I see the problem. In 2.15.x the constructor of ManagedRoute was changed
to: this.description = route.getDescription(), however before it was:
this.description = route.toString().
Where toString was defined as "EventDrivenConsumerRoute[" + getEndpoint() +
" -> " + processor + "]" (for
As an example in the prior version the getDescription() method would return
something like:
EventDrivenConsumerRoute[Endpoint[file://C:/JMS/gangplank/work/guard_ACK/?delay=1000=true=%23partialFilter=.error=none]
-> Pipeline[[Channel[convertBodyTo[byte[]]], Channel[RecipientList[Simple:
I'm upgrading an app from Camel 2.13.2 to 2.15.6 that uses Camel's JMX
support. Specifically we query for the various routes and leverage several
of the operations. The problem is the getDescription() operation now
always returns null. I have tried several of the 2.15.x versions and they
all
