Contents |
These are general deviations that purposely deviate from the CFML Standard.
By default Railo does not search the sub directories of the custom tag pathes for a certain custom tag. But you can enable it in the Railo web or server administrator.
Railo does not search for CFC's inside the Custom Tag directory
If the trusted cache is enabled Railo will not look for any new sourcecode data in the file system. Railo will always execute the last compiled version of a file. Opposed to the CFML standard, where the trusted cache can only be activated for the complete server, Railo offers the trusted cache also per single mapping. This is especially useful if an application uses a framework in which the sourcecode therefore does not change but the application still generates dynamic code. This is a most welcome advantage for several CMS-systems.
It is also possible to set custom tag directories to be trusted. They trusted cache rules apply to them accordingly.
Railo isn't capable to read crypted data of other CFML Engines. In order to nevertheless protect the own Codes Railo Archive (.ra) can be used. These make it possible to deploy codes ready compiled and in the case of RAS without the initial Source-Code. The only disadvantage of this method is in this case (.ras) errors which showed up during exploration no longer include source information.