Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of cwolf.algo@gmail.com
 designates 209.85.216.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1349777811189-5720789.post@n5.nabble.com>
References: <1349704082934-5720739.post@n5.nabble.com>
	<CAK=acOJy2D3Z9WuBLaG0D18aCOGDwFdaAvt6wKFwVOagxr4nhg@mail.gmail.com>
	<1349777811189-5720789.post@n5.nabble.com>
Date: Tue, 9 Oct 2012 12:45:21 -0400
Message-ID: 
 <CAK=acOJSoYObU-CEqPzp4ENLkFq+zwyrYs3Yu4-B8CzmLDYLYQ@mail.gmail.com>
Subject: Re: Jboss 7 and camel -bindy 2.10
From: Chris Wolf <cwolf.algo@gmail.com>
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Elz,

I was making a general suggestion as to a better way to do Camel
deployments on JBoss - i.e. not using WAR deployment, but rather
Spring AppContext deployment.  Sorry for not directly answering your
CSV question.  If I can, I'll try the Bindy component in one of our
JBoss deployments and let you know how it goes.  (Since that Bindy
component looks like we can use it in our app)
Feel free to send me a test input file.

Thanks,

   -Chris

On Tue, Oct 9, 2012 at 6:16 AM, Elezabeth <Elezabeth.gregory@ibsplc.com> wrote:
> Hi Chris,
>
> I dint understand quite well about your post.
>
> But one observation I would like to share here.  When I used CSV instead of
> Bindy. It worked.
>
>
> So is not some issue between camel bindy and JBoss 7?
>
> My issue still exists. Camel bindy is more powerful than camel -csv. Also
> csv doesn't match all of my requirements also. I am looking for some way in
> which I can make bindy work in JBOSS
>
>
> Thanks in Advance.
>
>
>
> -----
> Thanks & Regards
> Elz
> --
> View this message in context: http://camel.465427.n5.nabble.com/Jboss-7-and-camel-bindy-2-10-tp5720739p5720789.html
> Sent from the Camel - Users mailing list archive at Nabble.com.