Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of pras@dr.dk
 does not designate 216.139.236.26 as permitted sender)
Date: Mon, 8 Apr 2013 07:44:05 -0700 (PDT)
From: "Preben.Asmussen" <pras@dr.dk>
To: users@camel.apache.org
Message-ID: <1365432245918-5730510.post@n5.nabble.com>
In-Reply-To: <5162D281.2010407@gmail.com>
References: <1365360374231-5730476.post@n5.nabble.com>
 <5162D281.2010407@gmail.com>
Subject: Re: Camel Splunk component
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Hadrian

Yeah I know some of Apaches licence guidelines and fortunately the Splunk
SDK seems to be Apache licenced see
https://github.com/splunk/splunk-sdk-java#license
Damien Dallimore from Splunk has taken a look at the component and to quote
him 
_____________
I'm becoming a Camel fan. Haven't used it a great deal beyond simple hello
world stuff though I have to admit.

As powerful as Spring is , sometimes the jungle of declarative xml can
detract from simply being able to look at a few simple lines of code and
know whats going on.

I'll do simple blog , might lure in some collaborators even :)

_____________

That's kind of nice to hear - lol

There is also a maven repo for the sdk described at
http://blogs.splunk.com/2013/04/04/splunk-sdk-for-java-now-has-maven-support/
I havn't taken Splunk for too much of a spin, but it seems promising. 
My thoughts is atm. to use it in our integration projects for collecting
audit trails, and then build visualisation dashboards. I havn't come to that
yet though.

Regards,
Preben


--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Splunk-component-tp5730476p5730510.html
Sent from the Camel - Users mailing list archive at Nabble.com.