Railo Server 4.1 Beta Released!

March 1, 2013 · By Mark Drew · 5 Comments

The Engineering team have been busy over the last couple of months getting Railo 4.1 ready and we are pleased to announce that we now have a public beta of Railo 4.1 available!

Some of the highlights of this new version:

  • Create a Datasource Definition in the Application.cfc (RAILO-1935)
  • You can now enable full null support in Railo including the "null" keyword (RAILO-2194)
  • Great enhancement to multi-threading! Now all the each functions support the argument "parallel" (RAILO-2158)
  • Try it again! With help of "retry" you can reexecute a try block that had failed before (RAILO-2176)
  • More control with nested loops! labels allow you to specify which loop you refer to with "break" and "continue" (RAILO-2179)
  • Railo rocks! The new Elvis Operator ( ?: ) will help you to write faster and cleaner code! (RAILO-2195)
  • The missing piece! With help of the function componentListPackage() you can easily list all of the available CFCs of a certain package (RAILO-2307)
  • Keep it efficient! Using the attribute lazy="true" with cfquery will defer the loading of data to memory to the time you try to access it (RAILO-1641)


But that's not all:

  • Smart Whitespace management allows you to keep preformatted text in tags like <textarea> and <code> (RAILO-142)
  • Generate heapdumps easily with use of the <cfadmin> tag, (final release will have an option to do so from the Railo Admin) (RAILO-2162)
  • Full control of how Railo buffers suppressed output (RAILO-2157)
  • Per function setting of how the local scope should be handled using the 'localmode' attribute (RAILO-2142)


And Finally

  • Pass the attribute async="true" to <cfdump> and dump large objects to file without slowing down your script (RAILO-2185)
  • Ability to remove space between cffunction and cfargument (RAILO-2040)
  • New Function: queryColumnData as improvement over the function valueList (RAILO-2084)
  • Second parameter to the "round()" function allows to specify the precision(RAILO-2139)
  • Replace() and ReplaceNoCase() accept an optional Struct argument for populating text templates (RAILO-2160)
  • Add support for attribute "preauth" to cfhttp for more control over authentication (RAILO-2244)
  • Add support to define custom locale date/time formats (RAILO-464)
  • The Railo admin is now faster, by using a sprite for image loading (RAILO-2225)
  • Improved string based filters for cfdirectory (RAILO-2188)
  • The function fileCopy now support the argument overwrite to specify the handling of existing files (RAILO-2133)

You can find Railo 4.1 Beta in our Download Section

Over the next few weeks we shall go into each of these features and some other new items so that you can get the most of Railo 4.1!

Have fun with Railo!

Tags: New release · Railo 4.1

5 responses so far ↓

  • 1 Jonathan van Zuijlekom // Mar 2, 2013 at 3:20 PM

    Nice features!

    But why did I see this beta in the Stable Release update section in the Railo admin?
  • 2 Gert Franz // Mar 2, 2013 at 4:32 PM

    @Jonathan: Because it was an error and we have placed the file in the wrong directory :-) Apologies, and we have corrected ot
  • 3 Adam Cameron // Mar 10, 2013 at 8:43 PM

    In response to someone on Twitter having the same problem as I detail here, I downloaded the 4.1 beta install from this URL:

    I cranked it up, and ran this code (lifted in part from https://issues.jboss.org/browse/RAILO-2195):

    Z= x ?: 'Elvis';

    This errors with:

    Railo Error (java.lang.NoSuchMethodError)
    Message   railo.runtime.functions.decision.IsDefined.invoke(Lrailo/runtime/PageContext;D[Ljava/lang/String;Z)Z

    Has Elvis already left the building?

  • 4 Tony Garcia // Mar 10, 2013 at 9:53 PM

    I logged the issue in Railo's issue tracker:
  • 5 Steve // Apr 16, 2013 at 1:28 AM

    Nice release, and thanks for everything you do on Railo.

    One request (which I will happily post to a more appropriate spot if requested) - we use Railo as our test servers for a client that uses Adobe CF on prod. I know there are incompatible tags, but it would be nice to have a stopgap for some of them instead of a compilation error. For example, instead of failing on cftextarea, simply throw in an HTML text area, or allow developers to be able to conditionally include it based on server.coldfusion.productname.

    Thanks again for an awesome product.

Leave a Comment

Leave this field empty: