Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of krasserm@googlemail.com
 designates 74.125.82.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject
         :content-type:content-transfer-encoding;
        b=yFVvA7/Ug3ER1fXnIOchBQVRH35nhQ8zeE+V0RZewYrJw2uinMMGjvX5Jm0dy7IWrD
         QvI3vqYuAD9HuH3gGP5SE/ucmPtmNLf+xY08iFgHql39DX7Al7e2gYUQiIqVKbVi4nzA
         NSQkPlJzstxwSp8BNNqCdX4MfTlxRiKIe//2c=
Message-ID: <4D37F0BD.7060108@googlemail.com>
Date: Thu, 20 Jan 2011 09:22:21 +0100
From: Martin Krasser <krasserm@googlemail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de;
 rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: users@camel.apache.org
Subject: [INFO] Project scalaz-camel
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi,

I want to let you know of a new Camel-related project that I've been 
working on over the last couple of weeks:

scalaz-camel - A Scalaz-based DSL for Apache Camel [1, 2]

 From the docu: " This project provides a domain-specific language (DSL) 
for Apache Camel that is based on the Scala programming language and the 
Scalaz [3] library. It supports the combination of message processors 
and endpoints to complete message processing routes based on functional 
programming (FP) concepts such as continuations, monads and Kleisli 
composition. The scalaz-camel DSL is an alternative to Camel’s existing 
Java DSL and Scala DSL (it does not depend on the org.apache.camel.model 
package) ... [and]was re-designed from scratch with the goal of a better 
and more native integration with the Scala programming language." (find 
more at [4])

Over the last year I've been involved in Scala projects that use Apache 
Camel and was looking for a way to better utilize the power of Scala and 
functional programming concepts when creating integration solutions with 
Camel. The scalaz-camel project is a proposal how this could look like.

I'm posting this message because I'd like to hear your opinion about the 
approach taken by scalaz-camel. I'm also interested in your opinion 
whether you see a need for a stronger investment in supporting Scala and 
functional programming in Camel.

The scalaz-camel project is still in an early stage, some features (for 
production) are still missing (and documentation needs to be completed) 
but I hope the general direction is clear from the latest release 
(version 0.2). I'm also open for discussions about contributing 
scalaz-camel to Apache Camel.

Thanks in advance for any feedback.

Regards,
Martin

[1] https://github.com/krasserm/scalaz-camel
[2] https://github.com/krasserm/scalaz-camel/wiki#getting-started
[3] http://code.google.com/p/scalaz/
[4] https://github.com/krasserm/scalaz-camel/wiki

-- 
Martin Krasser

blog:    http://krasserm.blogspot.com
code:    http://github.com/krasserm
twitter: http://twitter.com/mrt1nz