While the cfeclipse team is working on giving support to the new scripting syntax added recently in cfml I falled into something that can help someone to have a better feeeling in the meantime.

I was not aware, until yesterday, that this syntax is supported in a script based cfc:

<cfscript>
component{
   
    public String function getname(String name="Andrea"){
        return name;
    }
    public String function getlastname(String lastname="Campolonghi"){
        return lastname;
    }
}
</cfscript>

So while it does not really looks "amazing" this will give you code colouring and syntax highlighting. But, most important, the syntax is fully supported from ACF and Railo too ( did not test on OpenBD ).

Some of you will be asking why to do that ? Just use cfbuilder .... and I agree. Cfbuilder is a great tool also if , in my opinion , lack of linux support. But I am one of those who are convinced that cfml deserves an open and strong ide to attract more developers so ... if you think like me consider to donate something to cfeclipse project.

One of the lack in the Railo world was the availability of an inline debugger. I always use fusion debug or internal cf inline debugger when using abode cf and sometimes I felt the lack of that developing with Railo.

The good news is that a railo compliant version of Fusion Debug will be available very very soon ( the public beta programm has just finished some week ago ). I had the opportunity to test the beta product and was working just fine as I expected it.

The functionalities are great and basically the same of the Fusion Debug version for coldfusion. Installation gave me some trouble that I easily solved on the google groups that the guys of Integral setted up to support .  

As far as I know the enterprise Railo edition will include a license of both Reactor and Debug products. I am a Fusion Debug license owner but I am not sure if the Railo product will need a license update or not. I am waiting the product release in the next weeks to check it. 

In conclusion I think that having an inline debugger available make Railo even more a robust solution.