Default

In Railo Version 4.1 we have put some thought into making your applications portable. One of most obvious things that comes to mind as a requirement for an application is defining the datasource(s) that it needs.

Already you can define the name of a datasource you are using by doing:

In version 4.1 we have enabled you to define the WHOLE connection string to the datasource in the Application.cfc file. The easiest way to see this is to actually create a datasource connection in the Railo Web Administrator. Once you have done that click on the "Edit" datasource button:

Then, at the bottom of the Edit Datasource screen you can see the snippet that you can use to actually define this datasource in the Application.cfc, for example:

You can now copy and paste that into your Application.cfc: delete the datasource from the administrator and use the "mydatasource" datasource as you would have done anyway!

The generated example above is the "native" way that Railo needs datasources defined. But this is not all, we have a "simpler" way to define datasources, and that is by giving it the fields you would expect in the administrator. So for the above example (where we used the class and connection string) we can also define it with the field names you would expect:

Default and Inline Datasources

Defining default datasources can also be done by using the this.defaultDatasource parameter. You can then either refer to a datasource you have defined: or create a datasource within the parameter itself :

Finally this is also true for ORM settings. You an define a datasource within your this.ormsettings structure too:

Side note about passwords:
You might notice that the password is encrypted in the "password" attribute. This is shown by the "encrypted:" prefix to the long string of code. What Railo has done is get your password and encrypted it. Making it safer to use within your code.

password:"encrypted:94fae38de2f70330df8ed879571bef699cd4bde7241f94f2309ee97fd0358be8".

Of course, you don't have to use encrypted strings. you can inou can replace the clear text password if you like rather than using the "encrypted:xyz" format.

Have fun with Railo!

Sometimes receiving an error is an indication, that something isn't in the stat you expect it to be. So we have introduced the new tag CFTRY. It comes with a set of jump statements which will be introduced in Railo 4.1 and which we will be blogging about soon. So let's start with CFTRY.

[Read more →]

Today we released the last release candidate for Railo 4.0. The following fixes have been made since version 4.0.0.013, which is the official download release at the moment.

[Read more →]

[Read more →]

[Read more →]

[Read more →]

With Railo 4.0 we have introduced the command line interface (CLI) that allows you to call .cfm files from your
current webroot. No webserver and no application server is involved when calling .cfm templates through the CLI.
For the moment this functionality is a little restricted but it will change until the final release of the CLI in Railo 4.0.

[Read more →]

Normally in patch releases we do not introduce new functionality. Except if they don't affect the runtime behaviour of Railo Server. With the latest release of Railo Server (3.3.1.007) we have introduced two new features I would like to present in more detail.

[Read more →]

For one of our clients we often need to process data in Railo returned by a query and reorganize them in a Pivot-Table like fashion. Normally what you have to do is to group queries by recurring values and sum them up depending on the values in the fields.

[Read more →]

We just came back from MuraCon in Sacramento that took place last week on Thursday and Friday (25th & 26th of August). We were represented by a larger portion of the Railo team. Sean, Mark, Tanja, Denny & Gert were present there and we met several people from the community to talk to them about Railo, how they use it and what things they would like to have in the next version. We were very pleased to hear that almost everyone told us how happy they are with the speed of the execution and the easy update process.

We were able to sort some bugs out with Greg Moser from Slatwall, so that now Slatwall works fine with the latest version of Railo 3.3 (which is 3.3.0.027) and we saw the excitment about the shortly upcoming release. We had some very interesting conversations with Matt Levine from Blueriver about the clustering capabilities of Railo and on how easy it is to use the clustered cache and the session storage. Mark, Denny and Gert showed off some of the great features of Railo 3.3 and 4.0 with the first demo of Railo 4.0 Alpha (in this case the CLI).

Mark's and Gert's slides.

Thank you everyone for visiting us at our booth and talking to us about Railo and on the different aspects on how to use Mura in an enterprise clustered environment. And many thanks of course to Blueriver who organized this great first Mura conference.

We will definitely be back next year.