If your lucky enough to have upgraded all of your CF servers to MX or redsky, the comments below don't really mean much. We here have a mixed bag of cf versions (we spend to much on contractors to upgrade software i'm told ...) from 4.5 through to redsky 6.1.
> Specifically in reference to: > 1) CFX tags > 2) Using Java objects with CF > 3) J2EE abilities - Servlets, JSP tags, EJBs, JMS etc. > 4) Combination of the above If possible I always use a cfx tag over cf equivalent code. I have found that a simple well written java tag is faster then poor performing cf code. I/O on cf 4.5 is a classic example. Post MX integrating java objects is quite a simple process. The ability to access core java packages from cfscript is quite amazing and well worth looking into. > Currently I've yet to find a reason to utilise my (probably very rusty) Java skills > within the ColdFusion environment. Used cffile recently to write out a large query object (pre mx)? Or how about cfhttp through a proxy (pre redsky)? > If you have utilised your (obviously less rusty) skills, why was it required? And why > did you choose the Java solution? Speed, performance. My 2 cents Rod --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/
