My favorites | Sign in
Project Home Downloads Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 88: Installation verification does not work
1 person starred this issue and may be notified of changes. Back to list
 
Project Member Reported by virtix, Mar 11, 2008
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
My bad! The index.cfm runs tests in the /samples/ dir, AND the samples _assume_
framework installation is directly under webroot. So, the installation verification
fails, giving the user the impression that the installation does not work. But in
fact it is ok, it's just the verification that's broken. Now, the error in mx8 or mx7
might be reported differently than in mx6. When debugging, MX8 pointed me to
TestSuite, which was a read hearing, but it's really the fact the smaples all extend
mxunit.framework.TestCase and that's why it fails. Will fix ASAP. 
Status: In
Mar 13, 2008
Project Member #2 virtix
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
Project Member #3 marc.es...@gmail.com
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
Project Member #4 virtix
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
Project Member #5 marc.es...@gmail.com
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
Project Member #6 virtix
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.

Powered by Google Project Hosting