Has cfmljure died?
seancorfield
The longer answer is that I had to take a break from blending CFML and
Clojure for a while to work on higher priority parts of the CFML
application. That stuff is almost complete now and we have the green
light to start incorporating Clojure code into the production
codebase. What that means is that cfmljure will get a lot of exercise
once we start that process (realistically starting mid-March) and an
updated version of the core CFC will be released, along with utility
CFCs that make it easy to manage Clojure dependencies using a bean
factory.
As we start to use Clojure more and more at work, I expect to settle
on some better patterns for CRUD operations and those will find their
way into the Task example that ships with cfmljure.
Furthermore, as I resume work on DI/1, I expect to provide a
convenient way to allow FW/1 controllers to be written in Clojure and
made available via a combination of DI/1 and cfmljure - in addition to
all three micro-frameworks being available and useful independently
(or in pretty much any combination).
Just wanted to provide an update on cfmljure since I lasted posted
about it back in November.
Sean
Sean Corfield
> The longer answer is that I had to take a break from blending CFML and
> Clojure for a while to work on higher priority parts of the CFML
> application. That stuff is almost complete now and we have the green
> light to start incorporating Clojure code into the production
> codebase. What that means is that cfmljure will get a lot of exercise
> once we start that process (realistically starting mid-March) and an
> updated version of the core CFC will be released, along with utility
> CFCs that make it easy to manage Clojure dependencies using a bean
> factory.
We've been in production for a while now with Clojure and we're very
pleased with the result. In fact, we're mostly writing new Model code
in Clojure and then just wiring it into the Controllers of the
existing app.
cfmljure has been through some radical changes - and radical
simplifications - and I hope to be pulling together a new release,
possibly this month (by mid-August at the very latest). The changes
mean that I'll have to redo the documentation and examples quite a bit
as I've streamlined the way we interact with Clojure.
> As we start to use Clojure more and more at work, I expect to settle
> on some better patterns for CRUD operations and those will find their
> way into the Task example that ships with cfmljure.
I'll probably try to rework the ORM we have created at World Singles
into a suitable open source library for cfmljure for use in the Task
Manager example although that may take longer. The ORM is based on the
standard clojure.java.jdbc library (which I'm lead developer for now).
> Furthermore, as I resume work on DI/1, I expect to provide a
> convenient way to allow FW/1 controllers to be written in Clojure and
> made available via a combination of DI/1 and cfmljure - in addition to
> all three micro-frameworks being available and useful independently
> (or in pretty much any combination).
At World Singles, we have a REST API in development built with FW/1
for View-Controller and Clojure for Model although we're currently
using ColdSpring (for historical reasons).
--
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
World Singles, LLC. -- http://worldsingles.com/
Railo Technologies, Inc. -- http://www.getrailo.com/
"Perfection is the enemy of the good."
-- Gustave Flaubert, French realist novelist (1821-1880)