Re: split, tokenize, unmarshal puts objects into ArrayList

What does your mapping file look like and what does the sample data look like? On Tue, Sep 13, 2016 at 8:11 AM, spurcell wrote: > Hello > > I am pulling in a StringBuffer into a exchange, splitting it on newlines > and > then converting each line into a dto with

split, tokenize, unmarshal puts objects into ArrayList

Hello I am pulling in a StringBuffer into a exchange, splitting it on newlines and then converting each line into a dto with the help of BeanIO. But when I look at the exchange it takes each exchange and wraps it into a ArrayList with my one pojo in it, per exchange. I googled this for a bit,

Issue with Big CamelContext XML configuration files

Hi , i have spring dsl based camel context xml file. file is around 5 MB due to some of the camel custom components has endpoint properties which has encoded XML content. bundles gets activated in OSGI container but not camel context. but same will work when size of xml is less!!!. while

Re: JMS Component configurations

I’ve done this a few different ways, but it depends on your routes and deployment technology. For example, when I’m deploying to a Karaf/OSGi container, I’ll create RouteBuilders that I can configure with the specifics of the environment, and then use Blueprint to configure the individual

Re: JMS Component configurations

Check out this page of the documentation: http://camel.apache.org/configuring-camel.html -- View this message in context: http://camel.465427.n5.nabble.com/JMS-Component-configurations-tp5787499p5787510.html Sent from the Camel - Users mailing list archive at Nabble.com.

RE: JMS Component configurations

Put that info in a bean? > -Original Message- > From: dpravin [mailto:pravin.deshm...@gmail.com] > Sent: Monday, September 12, 2016 9:32 PM > To: users@camel.apache.org > Subject: JMS Component configurations > > Hello All, > > We are in process of implementing hundreds of routes that

RE: How to set exchange headers from xslt.

Hi, With camel 2.10 you can't. XSLT has no notion about camel exchanges. If you were using Camel 2.17.1 or later and Saxon as the XSLT processor, you could write a Saxon extension function that could be added to the xslt endpoint with the saxonExtensionFunctions parameter. You can then get