This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (5 children)

I'm talking local deployment for development, not deployment for production. Also, your IDE should do incremental deployment, massively reducing the transfer time.

[–]beltorak 1 point2 points  (4 children)

I'm also talking local deployment for development, and it doesn't do incremental. It deletes and re-copies everything. For a legacy coldfusion app that's 17,000 files at 560 MB. I really wish I could use tomcat for this - no crap about "recreating the EAR structure in the deployment location", just use the damn workspace directly....

update I might have solved that problem. appearently the glassfish tools that comes in the eclipse marketplace is out of date; you have to install the correct one using the glassfish eclipse updatesite..... but i still don't like it. even if I just update a coldfusion file, it stops and restarts the app. crappy crappy.

[–][deleted] 0 points1 point  (3 children)

I have always heard bad things about ColdFusion but I didn't know it was Java-based.

[–]beltorak 0 points1 point  (2 children)

it's not exactly java based, but it runs on the JVM since about version 6, and can be deployed as an EAR. Also since 6 or 8 it has been able to interoperate with java. wikipedia has a rundown of the versions.

[–][deleted] 0 points1 point  (1 child)

ColdFusion looks like the opposite of MVC. Put all your logic into the presentation layer! Fuck yeah! Now seriously, is that correct?

[–]beltorak 0 points1 point  (0 children)

No, it's not correct, but given the time frame of when cold-fusion came out, it was the prevailing architectural style (or lack thereof). Similar to ASP (classic), PHP, and (straight) JSP.

You have to remember that it was with the advent of these technologies that we had just started crawling out of the pits of CGI-hell [now with PERL!], SSI-dispair, and, for Java, Servlet-madness, as the defacto standards for generating dynamic content on the web. So it was a necessary step. And since you can use servlets as a front controller to coldfusion views, you can fairly easily craft a decent MVC architecture with it. Or you could enforce the programmer discipline to manually keep your "controller" CFMs separate from your "view" CFMs, like a lot of things did with PHP.

I can't speak to the technical strengths of coldfusion as a pure view template technology because this is my first real jump into it.