The reason I asked is because now I have to set default Endpoint or URI in the producer template - it would be nice if the default setting would be the next down-stream endpoint.
On Thu, Apr 11, 2013 at 8:53 PM, Willem jiang <willem.ji...@gmail.com>wrote: > ProducerTemplate can send the exchange to any other endpoints. > Processor is decoupled with the camel route, I don't think you can get the > downstream endpoint from the custom Processor itself. > > > -- > Willem Jiang > > Red Hat, Inc. > FuseSource is now part of Red Hat > Web: http://www.fusesource.com | http://www.redhat.com > Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) > (English) > http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > > > > > On Friday, April 12, 2013 at 8:08 AM, Chris Wolf wrote: > > > Hello, > > > > I'm implementing a custom Processor - it will have a ProducerTemplate, > > which will always > > send to the next Endpoint, downstream - why do I have to set the > > defaultEndpoint > > or defaultEndpointURI? That guarantees hardcoding. Isn't there someway to > > indicate, > > upon CamelContext.createProducerTemplate() to imply next downstream > > Endpoint? > > > > It's not a show-stopper, I can explicitly configure the Producer > > defaultEndpoint, but I don't > > know why it can't default to the next down-stream consuming endpoint... > > > > Thanks, > > > > Chris > > >
