As an example I have created a very simple Hello World cfc and when I put the file into the webroot everything works fine:
However if I move the cfc into a directory below the webroot things get confused...
http://cftest.yoursite.net.au/cfc/hello2.cfc?wsdl - given an AXIS error, but
http://cftest.yoursite.net.au/cfc/hello2.cfc?method=helloWorld still gives the expected result
I wondered if there was a chance that the name of the directory could be an issue so I tried an alternative but there was no difference...
http://cftest.yoursite.net.au/cfxx/hello3.cfc?wsdl still give en error, and
http://cftest.yoursite.net.au/cfxx/hello3.cfc?method=helloWorld still works as expected
I've read quite a few posts about mappings and cfcs but con't find anything definitive. This is a multihomed server running Apache2.2 so I'm not sure how a mapping would help - unless there is something that CF needs mapped but I can't find a hint for that anywhere.
One other thing to note... I did edit the neo_xmlrpc.xml file to version 1 but the only effect appears to be that the error message says "AXIS error" for a version value 1 and "HTTP Status 500" for a version value of 2.
So, am I just missing a mapping? I even tried mapping "/" to the CF10 webroot but that had no effect.
In CF10 there is a new optional attribute (“wsVersion”) for the cfcomponent tag.
You can find it listed in the CF10 CFML Reference on page 98.
After the better part of two days trying to figure out why my components (when accessing them with Flex) would no longer function on CF10 I noticed this attribute. Once I changed my CFC files from “<cfcomponent>” to “<cfcomponent wsversion=’1’>” everything was fine.
I’m not sure if this will help in your situation but I see where you mentioned one of the error messages had referred to an “AXIS error”. Use of the AXIS 2 engine is noted in the reference.