The problem is not so much the mapping but the interpretation of the URL. The slash implies a directory structure. The only way I know to address this issue is to put in a front end Apache web server and have it do URL rewriting. I haven't gotten around to writing the technote on it yet - maybe this weekend. You would need to use JK2 (I don't think Macromedia supports this) or proxy module to forward the rewritten URL. e.g Translate the last / into a proper query string and then pass that on to the ColdFusion server. Unless ColdFusion supports URL rewriting - I think the non-J2EE CF had some script magic for this.
What if ColdFusion is the only application that I intend to run on jboss. Is there anyway then to send all requests to the CFMServlet? Wouldn't that allow my index.cfm/123 paths to work then?
I don't know enough about the CF port listener but I would assume that the CF port listener is receiving all your requests and trying to pass it to the correct CF servlet. However, due to the parsing rules for the received URL, the request router is having difficulty matching up a suitable servlet because of the implied directory value.
I would check a CF forum because I would think this is more CF specific than JBoss specific.
Try commenting out
<!-- The mapping for the default servlet -->
this from ur web.xml and retain the cfm mapping.
I was able to deploy ColdFusion MX 7.0 Enterprise as an .EAR onto JBoss 4.0.1. The context root of the ColdFusion application is /CFMX. What can I do to make ColdFusion the default?
Also, I created a test directory under the cfusion.war (which is under cfusionmx.ear) and placed a couple of cfm files and they work fine. However, when I placed a jsp file in the same directory, the JSP code does not get executed.
If anybody knows how to get this to work, please share it here.
Thanks in advance.