Railo 4.0 Beta Released!

July 2, 2012 · By Mark Drew · 2 Comments

Railo 4.0 Beta Released!

We are really proud to announce the immediate release of Railo 4.0 Beta! It has been months in the making and bringing over 100 new features, the Beta is finally open to the public!

This release of Railo Server brings with it a ton of features such as Closures, Rest services, Member Functions, Method chaining, Annotations and not to mention improvements to the core API, Compiler and Administrator interfaces.

You can check out more of the features in this release over at our website.

And of course, you download the fastest CFML server right now from our Download page!

New Features

Bundled with a bunch of new features that we find awesome we have really pushed the boat out in making this release. What new features you might ask? Here you go, a little run down on what we have prepared for you.

Loops get a make over

Loops have been the staple of the CFML language for years, in this release we have added the ability to use item and index in a <cfloop> statement. This now gives you access to a counter (defined by index attribute) and the actual item in the loop (defined in the item attribute)

Not content with just adding that, we have improved the behaviour of for/in loops so you can do statements like

for(item in Recordset){}

As if that wasn’t enough, we have finally added the group attribute to the tag, now you don’t have to switch out of using a <cfloop>to using a <cfoutput>!

Checkout more about Loops and CFLoop

Closures and functions are super charged

Closures are the ability to write anonymous functions that encapsulate the whole environment (enclose it) when you define a function. Developers have probably been using them for a long time without even noticing in JavaScript frameworks like JQuery. In Railo 4.0 you can now also use this power yourself!

Talking about functions, here is a simple but awesome feature for you, adding the the cachedwithin to <cffunction>! So simple yet so awesome. Your function output and return variables will now be cached for as long as you need them to.

Checkout more on Closures http://www.getrailo.org/index.cfm/whats-up/railo-40-beta-released/features/closures/ and Function Caching

Member Functions

For a long time we have been used to manipulating arrays, structures and queries using functions in the format of Array(), Struct() and Query*(). In Railo 4.0 you can now access these functions directly on your variable by calling them after the variable itself, for example, instead of doing ArrayLen(MyArray) you can now simply do MyArray.Len(). This goes for all the Array, Structure and Query functions.

If that wasn’t enough you can also iterate over items in an collection by doing MyArray.each(function(item){})! Isn’t that just awesome?

Check out more about Member Functions

Component Improvements

Components were not missed out either! We improved the creation of components by adding Implicit Constructors that allow you to populate a component without having to add your own init() code! Added to this you can add accessors to your components (those pesky get<em>()</em> and set() methods ) automatically and they will even allow you to chain set*() statements without the addition of a single character of code!

Check out more about Method Chaining and Magic Functions as well as Implicit Constructors over in our website

And Much much more!

There is so much more to Railo 4.0 Beta, why don't you download it today and check out more of the great things we have added such as Tags in CFScript, Rest services, Debugging Improvements, Annotations and much much more.

More to come soon!

We are so excited about this release we dedicated this whole newsletter to it! Stay on the look out for more news from Railo in the coming weeks! This is certainly going to be an exciting year!

Tags: Railo 4.0 · Release

2 responses so far ↓

  • 1 Alexey // Jul 3, 2012 at 10:11 AM

    Thanks Railo Team!!!
  • 2 aery // Jul 31, 2012 at 6:40 AM

    Hope railo team can do something about the documentation. tq

Leave a Comment

Leave this field empty: