Dave Watts <[EMAIL PROTECTED]> wrote: >> > What would you tell a ColdFusion user if s/he were to ask >> > what advantages they could utilize by moving to a J2EE >> > environment? >> >> platform and vendor independence, > >CF runs on Windows, Solaris, Linux and HP/UX now, and the next release will >probably run on everything that JRun runs on now. You can only get it from >Macromedia, though, as you point out.
You can't run a CF application on TomCat. You can run the same J2EE app on Jrun, J2EE Reference Implentation, Bea, IBM, JBoss, Orion .......... CF doesn't run on IBM AIX - yet. > >> speed, > >I have seen no reason to believe that J2EE is inherently faster, yet. > I have. The code is note being precompiled before it is executed. >> security, > >Huh? How is J2EE more secure? > Java is not typeless which in some cases be a security hole...(Dropping tables over the URL, a minor example) >> design patterns, > >Yes. CF is essentially batch programming - it's as far from OO as you can >get. > >> scalabilty. > >CF is plenty scalable, if done right, just like everything else. The problem is that it isn't done right often enough. Most people have an idea and go, and ColdFusion lends itself well to that. That's not a good thing in my opinion. The more you plan the less you program and the more mantainable the app is. Session Management in a Clustered enviroment. Building distributed applications. Ever write a Custom Tag and have it called from a none Web-Based Application? You can develop an EJB and have it used from a Web Container or a Client Application, you can send the bean out into the world and have it run in any compliant EJB Container. > >So, total score: 1.5 out of 5. I beg to differ. > >Note that I do think there are other valid reasons for using a J2EE >environment over CF, in addition to vendor independence and more elegant >code, such as ease of integration with other server-side components. That's one more point I forgot. total 6 out of 5. >On the >other hand, there are some great arguments for sticking with CF, such as >ease of maintenance and comparative labor costs. > A well designed Jave Application is also easy to maintain. It may take longer to develop then in CF, but there are advantages. Java is an industry standard and therefore I could imagine that a company willing to spend a million or two on an Inter/Extra/Intranet project is more likly to choose the J2EE platform. Let's hope that CF 6 will combine the best of both worlds. >Dave Watts, CTO, Fig Leaf Software >http://www.figleaf.com/ >voice: (202) 797-5496 >fax: (202) 797-5444 > > ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
