＋设为首页 ＋添加到收藏夹
the bigger question, of course is simply why a cfml developer would bother - or why a shop moving to j2ee would care - about preserving their cfml investment. theyre two sides of the same coin, but very different perspectives, and they hint at the two compelling reasons for running cfml on j2ee.
ill start with the more obvious reason: youre in a shop moving to j2ee anyway. but ill conclude (and spend more time) with an entirely different motivation: even if you dont know or care about j2ee, there are many benefits to deploying cfml on a j2ee server that we just dont get on a stand-alone cfml server.
the thing is, you wont hear any of these reasons explained to you this way by the typical advocates for j2ee.
reason 1: youre facing an organizational move to j2ee 【推荐阅读:Apache, Open Source,】
do you really know what it means to run cfml applications on a j2ee server? how does it work, and why would you bother? there are many benefits you may never have considered. in this article, the first of a series, ill answer these questions.
you may have heard that you can deploy your cfml on a j2ee server such as weblogic, websphere, jrun, or jboss - or on a servlet engine such as servletexec or tomcat. but what does this mean to a cfml developer, especially one whos not familiar with (or even interested in) j2ee?
whether youre an organization with multiple applications running on a single server, or a hosting company, or even if you have just one application on your current cf server, i hope this article will help you see when and where cfml on j2ee can make sense. ill conclude by pointing you to resources for learning more about this topic.
the two main reasons to run cfml on j2ee
... 下一页