Answering for myself, not for Dan: 1. Java is a squillion times faster than CF (OK, it's only about 200 times faster - might as well be a squillion) 2. That means it becomes feasible to create a truly cohesive OO domain model, which can be a lifesaver for large apps. 3. And once you have that domain model in a jar file, it can go anywhere - desktop apps, backend datasource for an LDAP server, suck it into .NET, trad JEE server...
Dunno about XML/XSLT for the front end, though. I reckon CF still rules there. Jaime > -----Original Message----- > From: James Holmes [mailto:james.hol...@gmail.com] > Sent: Thursday, 12 March 2009 1:32 AM > To: cf-talk > Subject: Re: Java Training: moving from CF to Java > > > Please forgive me the odd topic reply, but why on earth would > you want to do that? > > mxAjax / CFAjax docs and other useful articles: > http://www.bifrost.com.au/blog/ > > 2009/3/11 <coldfusion.develo...@att.net>: > > > > 1) We're moving our platform form CF to Java > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:320421 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
