Default

By default, variables defined inside a function or method are stored in the variables scope (of the template or the component). This can lead to threading problems if - for instance - a component is stored as a singleton in the application scope. Railo allows you to prevent this problem by controlling the local scope.

[Read more →]

Scope cascading, also known as scope precedence makes it easier for inexperienced developers to code, but slows down server performance. In Railo, scope cascading can be turned off.

[Read more →]

Railo Server creates a new web context for every website running on the same Railo instance. And since you have an individual web administrator available for each website, you can define different settings for each website which for instance allows you to configure two websites that they run in two time zones.

[Read more →]

This is a feature in Railo that confuses new Railo users very often. Railo comes with two types of administrators. In fact there are two type of administrators for every website you host on a system. In Railo all the settings you make in the Railo Web Administrator affect only the website you are calling it from. 

[Read more →]

Preserving your settings from one platform to another is as easy as copying some XML files.

[Read more →]

Configure your Railo archive to with resource proivder arguments

[Read more →]

Nic Tunney has a blog post on deploying Railo, Tomcat and Apache on Amazon EC2 Ubuntu AMI.

[Read more →]

Railo 3.3 brings a lot of new features. For us the most important one is Client/Session Scope Storage. Because of its importance let me introduce this feature first.

[Read more →]

 

With the release of Amazon's AWS Elastic Beanstalk service, it has never been easier to run Railo in the cloud. Amazon BeanStalk is a way to deploy Java Applications (which is what Railo is essentially) as war files into existing Tomcat containers that AWS manages for you. It also allows for easy scaling and balancing.

This tutorial will take you through setting up an environment that you can develop and deploy a sample application up to Beanstalk, rather than just a single WAR file.

 

[Read more →]

Before we begin the last part of the cache blog, let's do a little review.

In the first part, I have shown how the cache is used as an object cache, how to create a cache and interact with it but not more. The second part was on everything that is possible with the cache, and for what it can be used. In the last part we want to see at some special cases and deliver the promised reference.

[Read more →]