I am a bit late blogging about this but I had a quite 'intense' maech.

Since version 3.1.2.009 Railo starts the ajax tags support . You can read more here.

Ok so what's teh big news? What make me proud is that I developed those tags and after a long debugging they are finally part of the Railo core engine. The tags comes from the RailoAjax project that will go on focusing on the remaining ajax tags to fill the gap with ACF ( that's the plan .... but it's a long road to do ....).

This is an example of how a community effort can really contribute to the main project. I am sure more efforts will come in the future ... so if you an idea .... some spare time ..... and you wish to contribute do not hesitate to contact me .... Railo needs you.

Jordan Micheals has posted a great update to the Railo Installers project. 

Read more here.

Some of the bugs fixed/enhancements:

3.1.2.001-pl1 Patch Notes: 
-------------------------- 
- [NEW] IIS6 Is now fully supported on Windows Server 2003 
- [NEW] IIS7 Is now properly supported on Windows 7 machines 
- [NEW] IIS7/IIS6 now set "index.cfm" as a default document option 
- [NEW] Windows 64-bit is now available 
- [BUGFIX] Windows 32-bit Installer will now auto-detect 64-bit machines 
and will install the 64-bit connector when being installed on a 64-bit 
version of Windows. This is true for both IIS6 and IIS7. This avoids the 
  "LoadLibraryEx" failure in IIS if a 32-bit connector has been 
installed on a 64-bit version of IIS. 
- [UPDATE] The Tomcat connector has been upgraded from version 1.2.28 to 
1.2.30 (latest as of this release) 
- [UPDATE] The Tomcat Engine has been upgraded from version 6.0.20 to 
6.0.26 (latest as of this release) 
- [UPDATE] Source code in the Java JDK has been removed in order to 
reduce the size of the installers by approximately 20 MB. The installers 
now hover around the 100MB range. More rarely-used aspects of the JDK 
that ships with the installer may be removed at a later date in order to 
reduce the download size even more. 

If you are interested in Railo and you are thinking to take part of cf.Objective() you cannot loose this. Write 4k of amazing Railo code and win a ticket.

Two days ago I have posted some code that solve ( in part )  an annoying bug regarding caching in Model Glue framework.

As per MG docs the caching declaration can be used on any event-handler and include tag but, in practice. caching is only working if applied to the initial event-handler ( the first invoked by the url ). 

Since we want to use MG on our project, and we absolutely need a granular caching system, we are implementing  what we think can be a good solution and we would like to share for feedback and testings ( of course the MG team is the first in receiving our code for review and possible inclusion in future releases ).

We have made a new review to the first patch and now MG can support the following instructions:

<event-handler name="page.index">
<broadcasts />
<results>
<result do="views.one"/>
<result do="views.two"/>
<result do="template.main" />
</results>
<views>
<include name="three" template="pages/three.cfm" cache="true" />
<include name="four" template="pages/four.cfm"/>
</views>
</event-handler>

<event-handler name="views.one" cache="true"> 
<broadcasts />
....... 
<views>
<include name="one" template="pages/one.cfm" />
</views>
</event-handler> 

<event-handler name="views.two"> 
<broadcasts />
...... 
<views>
<include name="two" template="pages/two.cfm" />
</views>
</event-handler>

As you  can see from this code MG can cache a single views but , and this is the best feature I guess , is also able to cache a full event.handler even if that is not the initial event handler.

This solution can really speed up yout MG app reducing dramatically the effort you ask to your server to what your page exactly needs. Any time you are able to cache an "inner request" event MG will just include a bunch of html skipping any broadcasting and this can really save a lot of unnecessary server stress.

Over that imagine you can easily cache a full page excluding just the single lines that ( for example ) are reserved to logged user info/panel ( and of course skipping any unnecessary message broadcasting ).

You can find the patch here ( replace file /ModelGlue/gesture/eventrequest/EventContext.cfc)

Let me have your feedbacks and suggestions.

REMEMBER : THIS IS CODE SHARED FOR TESTING AND NOT FOR PRODUCTION USE.

As per my previous post about Xhtml Railo capabilities I will post my firsts experiences using Flying Saucer as enhancements of cfdocument tag.

Now, cfdocument is not bad but the rendering capabilities are quite limitated and when I discovered that cfdocument, up to cf9, do not support justified text alignment I decided to give a try with Flying Saucer.

The library works taking your xhtml and rendering that into a pdf processing your css.

Read more...