FW/1 3.5 early snapshot for testing
2 views
Skip to first unread message
Sean Corfield
May 18, 2015, 2:17:33 PM5/18/15
to framew...@googlegroups.com, cfml...@googlegroups.com
Hot on the heels of the first beta version of FW/1 3.1, I have FW/1 3.5 in a state where the brave and curious can start to experiment with it:
Download: https://github.com/framework-one/fw1/archive/clojure.zip
Out of the box, it works exactly like FW/1 3.1 (which is only a minor set of changes from 3.0.2).
Take a look at the new helloclojure example tho’ and you can see how easy it is to:
* Write a controller in Clojure instead of CFML
* Write a service in Clojure instead of CFML
In addition, this provides support for having Clojure services autowired into your CFML beans! Automagically!
We’re already running heavy tests on this version at World Singles with a view to taking it into production soon. This represents an important stepping stone for since we will be able to mix’n’match CFML and Clojure code all the way through the Controller / Model layers!
Caveats:
* There’s no documentation yet — I hope to have something up at the weekend… That’ll mean having 3.0, 3.1, and 3.5 all active on the documentation site! (3.5 is active now but is just a copy of 3.1)
* The mapping assumptions — /framework — are hard-coded right now, partly because the new ioclj.cfc extends framework.ioc so that it can override parts of it. Whilst FW/1 (one.cfc) can be anywhere and your Application.cfc can extend that path, going forward I think you’ll need a per-application mapping for /framework for rest of the components (and, yes, having a per-application mapping in place _before_ you try to create ioclj.cfc does work!).
Download: https://github.com/framework-one/fw1/archive/clojure.zip
Out of the box, it works exactly like FW/1 3.1 (which is only a minor set of changes from 3.0.2).
Take a look at the new helloclojure example tho’ and you can see how easy it is to:
* Write a controller in Clojure instead of CFML
* Write a service in Clojure instead of CFML
In addition, this provides support for having Clojure services autowired into your CFML beans! Automagically!
We’re already running heavy tests on this version at World Singles with a view to taking it into production soon. This represents an important stepping stone for since we will be able to mix’n’match CFML and Clojure code all the way through the Controller / Model layers!
Caveats:
* There’s no documentation yet — I hope to have something up at the weekend… That’ll mean having 3.0, 3.1, and 3.5 all active on the documentation site! (3.5 is active now but is just a copy of 3.1)
* The mapping assumptions — /framework — are hard-coded right now, partly because the new ioclj.cfc extends framework.ioc so that it can override parts of it. Whilst FW/1 (one.cfc) can be anywhere and your Application.cfc can extend that path, going forward I think you’ll need a per-application mapping for /framework for rest of the components (and, yes, having a per-application mapping in place _before_ you try to create ioclj.cfc does work!).
Sean Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
"Perfection is the enemy of the good."
-- Gustave Flaubert, French realist novelist (1821-1880)
An Architect's View -- http://corfield.org/
"Perfection is the enemy of the good."
-- Gustave Flaubert, French realist novelist (1821-1880)
Reply all
Reply to author
Forward
0 new messages