At least until CFX.01.... but honestly, jboss will likely be as invisible as jrun has been. When is the last time MOST of us have logged into the jrun console? I think the problem most big companies will have will be in the procurement office. Jboss is open source. No one to pay for support unless adobe is going to offer jboss support to cfx customers. IT procurement loves to pay for maint support. On Mar 11, 2011 2:19 PM, "Ajas Mohammed" <[email protected]> wrote: > Thanks Mark for sharing this. > > My first thought is we have CF 9 enterprise now and I guess if we move to CF > X, during installation, the installer will take over from JRUN and configure > Tomcat on our servers. I am certain lot of folks would say lets wait on > this. :-) > > > <Ajas Mohammed /> > http://ajashadi.blogspot.com > We cannot become what we need to be, remaining what we are. > No matter what, find a way. Because thats what winners do. > You can't improve what you don't measure. > Quality is never an accident; it is always the result of high intention, > sincere effort, intelligent direction and skillful execution; it represents > the wise choice of many alternatives. > > > On Fri, Mar 11, 2011 at 12:50 PM, Mark Davis <[email protected]> wrote: > >> Not sure how many here have seen this? >> >> >> >> http://www.coldfusionjedi.com/index.cfm/2011/3/3/ColdFusion-X-Writeup >> >> >> >> Today at Scotch on the Rocks, Adam Lehman released some tidbits about the >> upcoming new release of ColdFusion, ColdFusion X. I tweeted as much as >> possible, but for those who don't use Twitter, and for those who want a >> general one page summary they can comment on, here is what he said and my >> opinion where applicable. Please note that anything announced today could >> easily change between now and the real release. Also remember these notes >> are based on my memory of what Adam said. Any mistakes are my fault. >> >> 1) Verity will be removed. >> >> Not much to say about this. Adam suggested anyone using Verity now should >> begin looking into transitioning to Solr. Even if Verity wasn't being >> removed I think most people would recommend this anyway. Verity *was* a >> good product. I don't think it got the credit it deserved. But it's ancient >> now and Solr is much more capable. >> >> 2) JRun is being removed in favor of Tomcat. >> >> Not much to say about this one. I've used Tomcat before and it seems ok - >> but I've had issues with it and Apache. Hopefully that won't be a problem. >> Adam said - multiple times - that Adobe would be supporting Tomcat so that >> if you had issues with ColdFusion and Tomcat you won't be left out in the >> cold. I'm guessing this will be a slightly painful transition the *first*time and then after that - not much of a big deal. Unofficial reports are >> that ColdFusion runs much faster over Tomcat so any 'free' speed boost is a >> good thing. >> >> 3) Webservices updated to Axis 2. >> >> Anyone who does much with web services in ColdFusion will know that it's >> use of Axis 1 leads to issues with many service providers. ColdFusion X will >> upgrade Axis to 2.latest while keeping support for Axis 1 as well. It was >> suggested that in ColdFusion 11 Axis 1 would go away completely. This update >> will help enable Exchange 2010 support. >> >> 4) Scheduled tasks updated. >> >> Scheduled tasks will support chaining (run task B when A is done), >> conditions (don't run if CPU is 80% busy), priority, and grouping (consider >> A, B, and C a group and do this to them as a whole). Also - finally - you >> will be able to make them application specific. >> >> 5) Jobs >> >> Basically you wrap a set of code in a cfjob tag and it runs asynchronously. >> It gets added to a queue you can introspect and modify. Basically a >> shorthand for cfthread but with more control over the queue stack. >> >> 6) Java loader/proxies. >> >> No more need for JavaLoader - you can now load jars/classes via a This >> scope attribute in the Application scope. On the Java side, your Java code >> can create an interface from a CFC. Both seem like really nice, useful >> updates. >> >> 7) Closures. >> >> Ok, I'm on the fence on this one. I load closures in JavaScript. I honestly >> don't know how much I'd use them in a server side language. I'm sure I'll >> regret saying that though and I bet I'll wonder how I ever lived without >> them. Then again, it could end up being the next cfinterface. It was hinted >> that the implementation could be similar to what Mark blogged< http://blog.mxunit.org/2010/01/what-would-your-cfml-look-like-with.html>about a few months ago. >> >> 8) HTML5/jquery >> >> Nothing concrete was said here, but it was stressed that HTML5 and jQuery >> would be supported in big ways. >> >> >> >> -- >> You received this message because you are subscribed to the "Houston >> ColdFusion Users' Group" discussion list. >> To unsubscribe, send email to [email protected] >> For more options, visit http://groups.google.com/group/houcfug?hl=en > > -- > You received this message because you are subscribed to the "Houston ColdFusion Users' Group" discussion list. > To unsubscribe, send email to [email protected] > For more options, visit http://groups.google.com/group/houcfug?hl=en
-- You received this message because you are subscribed to the "Houston ColdFusion Users' Group" discussion list. To unsubscribe, send email to [email protected] For more options, visit http://groups.google.com/group/houcfug?hl=en
