Railo

People already know how well Railo does at running existing CFML code. In this contest we will challenge you to look into some of the cool Railo only features to see what you could code in just 4kb (about 100 lines of code) using Railo. We'll ... [More] post/comment on all submissions, and the winner gets a free ticket to cf.Objective(). Email your entries to [email protected] before April 1st (anywhere in the world) for a chance to win! Have a look at the additional Railo features here: http://www.railo.ch/blog/index.cfm/2009/11/26/Release-notes-Railo-312 http://www.getrailo.org/index.cfm/documentation/new-in-railo-31/ http://www.railo.ch/blog/index.cfm/2008/9/9/Railo-30-released--Features-part-1 http://www.railo.ch/blog/index.cfm/2008/9/10/Railo-30-released--Features-part-2 http://www.railo.ch/blog/index.cfm/2008/9/30/Railo-30-released--Features-part-III--Multimedia http://www.railo.ch/blog/index.cfm/2008/10/10/Railo-30-released--Features-part-IV--Task-manager-Remote-synchronization http://www.railo.ch/blog/index.cfm/2008/9/3/Extension-Manager http://www.railo.ch/blog/index.cfm/2008/3/31/S3-with-Railo http://www.railo.ch/blog/index.cfm/2008/2/28/Railo-Rewrite http://www.railo.ch/blog/index.cfm/2008/2/19/Creating-Railo-archives http://www.railo.ch/blog/index.cfm/2007/12/17/New-stuff-in-the-latest-releases--Part-II http://www.railo.ch/blog/index.cfm/2007/11/21/New-stuff-in-the-latest-releases http://www.railo.ch/blog/index.cfm/2007/1/9/Railo-Features-Part-V http://www.railo.ch/blog/index.cfm/2007/1/8/Railo-Features-Part-IV http://www.railo.ch/blog/index.cfm/2006/12/21/Railo-Features-Part-III http://www.railo.ch/blog/index.cfm/2006/12/20/Railo-features-Part-II http://www.railo.ch/blog/index.cfm/2006/12/19/New-features-introduced-with-Railo http://www.railo.ch/blog/index.cfm/2006/12/15/Railo-archives http://www.railo.ch/blog/index.cfm/Features Some additional ideas, Maybe someone wants to write a new cool debugging template: http://www.railo.ch/blog/index.cfm/2007/3/8/Debugging-with-Railo Update: Being programmers, we prefer more details. A question of white space came up on the mailing list. Gert's response was, "The compiled class needs to be within 4K." Hope this helps someone considering this challenge for an awesome conference ticket. [Less]

Gert announced tonight on Twitter that we're looking to get a pre-release group together to get feedback on Railo's ORM / Hibernate feature. If you're interested in being part of this pre-release group, please contact us. Please note, that the full ... [More] cfml scripting support is not available yet in Railo, so your existing ORM coding may require some changes. [Less]

So, this is probably confusing to some and I thought I'd try to clear this up. It's possible to setup Railo to run a task every x hour, minute and/or even seconds. You'll want to log into your machine and go to the Scheduled Task page ( e.g.: http://{your server}/railo-context/admin/web.cfm?action=services.schedule ) [More]

Andy Jarret recently blogged about the usage of this.datasource in Application.cfc. Just goes to show, it pays off reading the patch notes sometimes because it has been there for awhile ( since version 3.1.0.018 ): [000059] add support for default ... [More] datasource to cfapplication/application.cfc Go visit Andy's blog post for more details on how to use this.application. :) Another brief note is that this may be changing slightly in the future, but will always support the ACF Style ( this.datasource = "[some string]" ). [Less]

I am happy to say that at this year's CeBIT in Hannover, Germany we are joining the stand of our partners Contens and Intergral. We are very proud that both Contens and Intergral are increasingly relying on Railo as a CFML engine. If you like to ... [More] visit us, we have many new things we can show you and we might even help you with some problems. If you need any assistance from the best Railo programmers come see us in hall 6 stand J32. On one of the days Mark Drew will be there as well. We're looking forward to seeing you in Hannover in 2 March! If you want to meet us there either contact us or fill out the form on the contens homepage. Read the full press release by Contens. [Less]

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 ... [More] 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. Of course you know that the entire cache implementation was not our idea, but this is part of the CFML2009 specification and implemented accordingly in Adobe ColdFusion. For this reason, we could not make the implemnetation completely free of restrictions but had to follow a certain interface (tag and function interface). However, we have extended our implementation with some features that seemed important and which resulted in the alpha testing. The biggest difference lies in the fact (described in part 2) that you can create as many caches as you want. In addition you have several different cache implementations available as extensions. Railo itself uses the cache as a backend for cached queries, templates and ram resources. Next to these Railo offers a variety of optimizations for the existing "Object Cache" implementation. I guess it's best if we mix the special cases with the reference, and start with this it Features that are not specified in CFML2009 and do not exist in Adobe ColdFusion, are marked in red. cacheClear([string filter[,string cacheName]]) Flushes the cache. You can specify a key filter for the elements in the cache to flush, the filter follow the same rules as for cfdirectory-filter. With the second Argument you define the cache instance used by name (by default the "default Object Cache" is used). cacheCount([string cacheName]) Returns a count (integer) of keys stored in the cache. With the first Argument you define the cache instance used by name (by default the "default Object Cache" is used). cacheDelete(string id,[boolean throwOnError[,string cacheName]]) Deletes a single element from the cache, the id of the element can also contain a ",". With the second argument you can define if the functions throws a exception when the element does not exist (default is false). With the third Argument you define the cache instance used by name (by default the "default Object" Cache is used). cacheGet(string id[,boolean throwWhenNotExist[,string cacheName]]) Returns a element from Cache that match the given key. With the second argument you can define if the functions throws a exception when the element does not exist (default is false) With the third Argument you define the cache instance used by name (by default the "default Object" Cache is used). cacheGetAll([string filter[,string cacheName]]) this function return a structure containing all elements inside the cache. You can specify a key filter for the elements with the first argument, the filter follow the same rules as for cfdirectory-filter. With the second Argument you define the cache instance used by name (by default the "default Object" Cache is used). cacheGetAllIds([string filter[,string cacheName]]) this function return a array containing all keys inside the cache. You can specify a key filter for the elements with the first argument, the filter follow the same rules as for cfdirectory-filter. With the second Argument you define the cache instance used by name (by default the "default Object" Cache is used). cacheGetMetadata(string id[,string cacheName]) returns a structure with some Metadata regarding the cache elements (keys returned depends on the Cache type used). With the second Argument you define the cache instance used by name (by default the "default Object" Cache is used). cacheGetProperties([string type]) returns array with different properties about the cache (keys returned depends on the Cache type used). first argument "type" define to whitch cache instances information are returned "" or not set - information to all default caches (object,template,resource,query) "object" - information to "Default Object" Cache "template" - information to "Default Template" Cache "query" - information to "Default Query" Cache "resource" - information to "Default Resource" Cache <cache name> - information to a specific cache cacheKeyExists(string key,[string cacheName]) Returns true/false whether the cache contains an element with the certain keyname. With the second Argument you define the cache instance used by name (by default the "default Object" Cache is used). cachePut(string id,object value,[timespan timeSpan[,timespan idleTime[,string cacheName]]]) puts an element with a id into the cache, with a life time and an idle time. With the 5th Argument you define the cache instance used by name (by default the "default Object" Cache is used). cacheRemove(object ids,[boolean throwOnError[,string cacheName]]) removes elements from cache defined with argument ids, this can be a string list of multiple elements or a array containing keys. With the second argument you can define if the functions throws a exception when the element does not exist (default is false). With the third Argument you define the cache instance used by name (by default the "default Object" Cache is used). cacheSetProperties(struct type) sets some properties for a certain cache (settings depends on cache type used). This function is not supported by Railo, because we see this as a security risk, you can modifie cache configuration wihout a password, you can use tag cfadmin instead. we will add support for this function in a future release, but then you can enable,disable this function in admin for every single cache instance. cfcache> This tag has two functions: you can manipulate data in the "Object Cache" (just like the functions cacheGet, cachePut, cacheClear) by using the actions "get, put, clear". In addition, you can still use it to cache pages as well. With the attribute "cachename" you define the cache instance to be used by its name (by default the "default Object" cache is used). Now we see that Railo not only uses the cache for different purposes, but also thet the possibilities of the object cache have been greatly expanded. For us, however, the are many more ways in how the cache can be used. Whe have already thought of other use cases for the cache. One idea is to use the cache as a backend for the client scope where instead of a database you could use a cache for it as well. If you have a good idea where it would make sense to use the cache as well please let us know. [Less]

In the first part of the cache blog entry we looked at how we can use the cache directly without entering into great detail. Now let's have a look at what the cache is at capable of. Because it provides much more than just storing data. [More]

It is long overdue, but a tutorial on how to create your own Railo extension provider is now available on the wiki. Why would you ever want to build your own extension provider? Perhaps you are a framework developer and you want to provide your users ... [More] running Railo a 'one-click' installation / update. Perhaps you are managing several Railo servers and you want your internal servers to update to your the latest application / custom cfc / built-in-tags/functions, etc. If you're unfamiliar with what Railo extensions are, they're essentially plug-ins that are available via the Railo team or with the help of the tutorial, you can create your own. If you want to see Railo extensions in action, you can log into your own web context ( http://{YOUR SERVER}/railo-context/admin/web.cfm?action=extension.applications ) and Railo will instantly download and install the many available frameworks (ColdBox, Fusebox, Model Glue, ColdSpring, Mach II, cfwheels, etc.) and applications ( Farcry, Mura, Galleon, Mangoblog, etc).The Railo team also offers paid extensions (Amazon S3, cluster scope, admin sync, cfvideo and more) via the server context ( http://{YOUR SERVER}/railo-context/admin/server.cfm?action=extension.applications ). [Less]

Since version 3.1.2 Railo supports the possibility of using a cache. This blog entry will go into the details of this feature. The blog is divided into 3 parts, the first part will deal with the base functionality, the second part show how the cache ... [More] is used in backend and the last part takes care of specialties when using the cache and shows a reference. [More] [Less]

I'm actually hesitant to post this because the Railo team is actually trying to make progress on documentation and we have some new documentation policies in place. However, I know if I don't post this and people eventually find out about it, they'll ... [More] wonder why they didn't know sooner. This tip pertains to Railo's createObject('java') implementation. I'm told that it has been there for awhile, but I couldn't tell you what build it came from. I'll share the code and go from there. <cfset object = createObject('java','path.to.package.classtoinvoke','/path/to/jar/file/on/system')> Read that line 2 or 3 times and let it sink in a little. Yes, Railo's createObject('java') has a 3rd (and 4th) argument. This is the full documentation on this from Michael is: createObject('java',String className,String paths, String delimiter ) - 'java' (required) - className (required) - the full class name (class and package) of the class to invoke. - path (optional) - a list of jar files and directory that contains class files - delimiter (optional) - delimiter used for the path list (default is comma ",") Sean Corfield will be presenting this to the opemcfml.org advisory board, whether it gets voted on or not remains to be seen. Also, please note that I'm making Documentation/Wiki a high priority for the year 2010. [Less]