CF10 on JBoss7 going though IIS7, CF can't find cfm file in the website root.

Question

Our currently environment is CF8 running using JRun4 (via the wsconfig tool ) with IIS 6.0 has the webserver. We are trying to migrate our environment to CF10 using JBoss7 as the processing engine with IIS7 as the webserver.
We have managed to configure the ISAPI Connector so that IIS sends .cfm, requests to JBoss7
The issue we are running into is that when calling a .cfm file ISAPI Connector, ColdFusion cannot fine the file inside the IIS website root. Yet if the cfm. file resides in the cfusion.war root, then ColdFusion finds the file and processes it.

Answer 1

HI! I'm using jdk1.3 on WINDOWS 98. I'v made two
classes in same package.Compiling of first class was
ok but when i tried to compile second class (which
uses first class) I get the message: can not resolve
symbol: (name of first class). I'v tried to put these
classes in same folder but it still doesn't work.I'v
tried with javac -classpath. but i get the same
message. Please help!!!!!!!!!!!You might need to post your directory structure. Let's say you have "package mypackage;" as the first line in both files. Let's call the files ClassA and ClassB. Then you need a directory named mypackage. Put the successfully-compiled class ClassA file into it, or put both .java files into it.
Now the compiler needs to be able to find the .class file or at least be able to find the .java file. To find a dependent class, the compiler looks through the directories in the Classpath for the fully qualified class name. Fully qualified means package name plus class name. In my example, if compiling ClassB requires ClassA, the compiler looks for mypackage.ClassA. So if the mypackage directory is in c:\myjava (meaning the file path to ClassA is c:\myjava\mypackage\ClassA), then c:\myjava must be 'in' your Classpath.
If you do not have a Classpath set on your system, the default is the current directory. So you could "cd c:\myjava" then "javac mypackage\ClassB.java" If you do have a Classpath, then you could add c:\myjava to your Classpath. Another option is "javac -classpath c:\mypackage ClassB.java"