Yeah I came across this today actually, very annoying.

Can someone explain what the benefit is of writing cfcomponents as
pure script is ? What does it allow you to do that you can't with
cfcomponent tag , cffunction tag and using cfscript within your
function bodies ?

Reason I ask is it strikes me that often things are rewritten because
we can use new functionality rather than it offering any inherent
benefit ?

But as i said i maybe missing the obvious.

Alex

On Jul 11, 6:20 pm, Sean Corfield <[email protected]> wrote:
> On Mon, Jul 11, 2011 at 7:12 AM, Matthew Woodward <[email protected]> 
> wrote:
> > Alan or Andy will have to confirm but I'm pretty sure script-based
> > components aren't supported yet.
>
> Do the OpenBD team have an ETA for adding that compatibility?
>
> FW/1 1.x supports CFMX7 / 8 / 9, Railo 3.1 / OpenBD 1.2 (from 11/30
> on). FW/1 2.0 supports ACF9.0.1 (not 9.0), Railo 3.2. I'd like to
> point folks at an OpenBD version that would support it.
> --
> 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)

-- 
official tag/function reference: http://openbd.org/manual/
 mailing list - http://groups.google.com/group/openbd?hl=en

Reply via email to