FusionDox is a web based enterprise document management platform. Out of the box, FusionDox provides an intelligent document library that indexes and organizes your documents, lets you design business forms, create workflows and automate business processes.
As a platform, FusionDox lets you design structured business content, and provides many tools to optimize business communication and knowledge collection. With this information, we provide tools for sharing and re-using information so that you can quickly find the content and documents you need. FusionDox can be used as the back-office platform for custom web applications, intranets and websites, as well as for authoring content that gets remotely published to any of these types of systems as well. It has a powerful SOA based API, and is easy to develop against using any modern programming language.
For end users, FusionDox is hands-down the easiest document management platform to use, and includes our patent pending one-click live editing technology for users to edit documents (such as Microsoft Office, Open Office, Quickbooks, Adobe Illustrator, and more) directly through the web browser. Our web tools work with Internet Explorer and Firefox browsers on Windows, Macs and Linux PCs. The FusionDox engine was designed to be customized; so many aspects of how business forms, reports and views are designed can easily be customized, extended or replaced with custom layouts.
Information and requests for demos are available online at http://www.fusiondox.com
We have been working with CFML for well over 10 years, and we have built many tools that extend our CFML applications. We have 12 years of Java experience as well, and have written several applications directly in Java for our customers. We have been working with Railo since version 2, for about 18 months. We are using Resin for now. We have had requests for deploying on Websphere and JBoss.
When we heard Railo 3.1 was going open source, we were very excited! For a long time we have struggled with sales when customers liked our platform, but were disinclined to use our platform because of the requirement to purchase Adobe ColdFusion. We now can offer a solution that takes advantage of all the same technology at an easier entry cost.
Overall the process of transitioning to Railo was a delight. All of our CFML code (with the exception of error handling templates) worked perfectly with no modifications required. We have since implemented a different error handler template which addressed that issue. All remaining issues were where we had implemented custom Java extensions to CFML that needed updated for use with Railo. In particular, we used a custom implementation of Lucene, and simply needed to update our code to work with the more updated version included with Railo 3.1.
Once our port of the system was done, we did some testing and found the performance to be excellent. There was clearly a noticeable difference in speed, and all features of our software ran much faster and snappier on Railo than on ColdFusion 7 or 8.
The technical hurdle for us was the process of updating our code that used custom java JAR files to work with newer JAR files included with Railo and that was resolved within a week without needing any assistance from the Railo team. Also, documentation on how to setup a clustered system using Railo seems to be difficult to find, and has prevented us from setting up a clustered environment so far.
The feature in Railo that we really like is the separated web and server admin contexts so that customer data and resources are isolated. We are looking forward to the upcoming Hibernate ORM integration support.
Performance and price were the top reasons for choosing Railo. Being able to talk to Railo team members has helped considerably, and we consider them a significant resource, which we have not had with other products. The advice we would have for someone coming into Railo, would be to jump in full force, and any functionality that doesn't exist in Railo today, to use open source Java to extend it. This way code built on Railo + Java should work on Adobe's platform as well if necessary. This is opposed to implementing CF8/CF9 specific code, and then having issues deploying on Railo later.