| Issue 88: | Installation verification does not work | |
| 1 person starred this issue and may be notified of changes. | Back to list |
|
What steps will reproduce the problem? 1. Download and install framework a couple of dirs deep in webroot 2. Run /foo/bar/mxunit/index.cfm What is the expected output? Success and several tests run What do you see instead? In MX 8: Ooops! There was a problem with running the installation test These are the errors as reported by ColdFusion: Type: Application Message: Could not find the ColdFusion Component or Interface mxunit.framework.TestCase. Detail: Ensure that the name is correct and that the component or interface exists. In MX 6: Ooops! There was a problem with running the installation test These are the errors as reported by ColdFusion: Type: Application Message: The name .framework.TestSuite is not a valid component name. Detail: Component names cannot start or end with dots. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mar 11, 2008
Project Member
#1
virtix
Status:
In
Mar 13, 2008
This turns out to be a couple of issues and is bringing to light some potential others. I was able to fix the issue where the install was using the samples, which assume installation directly under web root by generating a test file and writing it the pwd and running that. This seems to work mostly. I was also able to reproduce the issue of the problem where getMetaData() is not returning correct info on on components under Apache 2.2. This may prov to be a bigger issue. Just install /mxunit/ in htdocs and fire up index.cfm. I have also been trying to use the CFCProxy class and have had some good success. It allows you to load CFCs via a file path instead of the dot notation. This may be very useful for addressing installation location issues.
Mar 13, 2008
rad. i was wondering about that cfcproxy myself. i'm glad you found it and are having success. nice job man. getting things to work at any path in any environment has been a goal of yours all along, i know, and it's a noble one. difficult, but noble. good job bill.
Mar 17, 2008
done... but cfcproxy does not work in cf6. Ok for now, as the installation verification page is only that. I threw an unsupportedversionexception if the user attempts to run it in cf6.
Status:
Fixed
Mar 24, 2008
is there a way, for cf6, to just make a more basic page then? like... do it without the proxy and have a message saying "if you have problems with component paths, do X and Y"?
Mar 25, 2008
What I did in the most recent build is to thrown the unsupported exception, catch it, and display somewhat friendly message ... We could make the message more friendly. But the page does not "break" per se. |
||||||||||