View comments | RSS feed

Disabling JSP functionality (server configuration only)

ColdFusion MX 7 Enterprise Edition provides support for JavaServer Pages (JSP) technology through the underlying J2EE application server on which it runs. Because JSP code runs outside of the realm of the ColdFusion MX 7 security framework and, therefore, is not subject to ColdFusion MX 7 sandbox security, you do not typically deploy JSPs in a shared, hosted environment where more than one customer shares a single server.

To disable JSP functionality:

  1. Open cf_root/runtime/servers/default/SERVER-INF/default-web.xml in a text editor.
  2. Find the servlet-mapping entry for JspLicenseServlet.
  3. Comment out this entry, as the following example shows: 
    ...
<!--
	<servlet id="macromedia_servlet_8789">
		<servlet-name>RDSServlet</servlet-name>
		<display-name>RDS Servlet</display-name>
		<servlet-class>coldfusion.bootstrap.BootstrapServlet</servlet-class>
		<init-param id="InitParam_103401311065856789">
			<param-name>servlet.class</param-name>
			<param-value>coldfusion.rds.RdsFrontEndServlet</param-value>
		</init-param>
	</servlet>
-->
...
  4. Save and close the file.
  5. Restart ColdFusion MX 7.

ColdFusion MX 7 | ColdFusion MX 6.1 | ColdFusion MX | Forums | Developer Center | KnowledgeBase | Bug Reporting

Version 7

Comments


serat said on Apr 25, 2005 at 4:40 PM :
Should this config file snippet show the JspLicenseServlet mapping instead of the RDS Servlet mappping? (see also 54861)
ASandstrom said on Apr 26, 2005 at 1:39 PM :
In response to serat:
You are correct. The code snippet should appear as follows:
<!--
<servlet>
<servlet-name>JspLicenseServlet</servlet-name>
<servlet-class>coldfusion.license.JspLicenseServlet</servlet-class>
</servlet>
-->
alexhubner said on May 18, 2005 at 1:13 PM :
It's also a good idea to remove the extension mapping in the webserver (IIS/Apache).
naMwodahS said on Aug 18, 2005 at 10:46 AM :
Should you also comment out the <servlet-mapping> entry as noted in the doc:
<!--
<servlet-mapping>
<servlet-name>JspLicenseServlet</servlet-name>
<url-pattern>*.jsp</url-pattern>
</servlet-mapping>
-->
plum1120 said on Dec 20, 2005 at 9:35 AM :
We are running CFMX 701 Standard alongside NES 6.1. In the past, there were a series of steps required to permit NES to handle JSP parsing. These steps no longer work in CFMX 701. CFMX continues to throw a license exception, even when jsp support has been commented out of CFMX (default-web.xml) and the necessary edits have been made to the NES config (obj.conf). It is imperative that we have control over which engine parses .jsp's as we have had in the past. The online documentation DOES NOT WORK; it is a re-hash of the steps I have described above, and it was clearly copied from the CFMX 6.x documentation and not tested. Please tell me I'm wrong or have missed something.
jrunrandy said on Dec 21, 2005 at 4:53 AM :
I spoke with one of the developers and this is what he said:

With CF 7.x standalone- to disable JSPs, it is not sufficient to comment out the JspLicenseServlet in

"cf_root/runtime/servers/coldfusion/SERVER-INF/default-web.xml"

The same entry needs to be commented out in "cf_root/cfusion/wwwroot/WEB-INF/web.xml" also.

 

RSS feed | Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/coldfusion/7/htmldocs/00000054.htm