For MachII to work properly you must have the framework in the proper
location for CFMX to find the CFCs. Basically, you need to extract the
framework and sample application under your webroot like this:
c:\inetpub\wwwroot\MachII
c:\inetpub\wwwroot\ContactManager
This is because MachII (and thus CFMX) expect to find the CFCs in a certain
place. Let's look at a line of code from mach-ii.cfm within the MachII
folder:
<cfset application.appLoader = CreateObject('component',
'MachII.framework.AppLoader') />
This tells CFMX to look for the AppLoader CFC in MachII\framework\ under
your webroot. For Mike this would be:
c:\inetpub\wwwroot\MachII\framework\AppLoader.cfc
Now let's look at mach-ii.xml from ContactManager\config\:
<listener name="ContactManager" type="ContactManager.model.ContactManager">
This tells the framework to find the ContactManager CFC in
ContactManager\model\ under your webroot. Again, for Mike this would be:
c:\inetpub\wwwroot\ContactManager\model\ContactManager.cfc
Just remember that the dot notation for CFCs is just referring to folders
within your webroot:
MachII.framework.AppLoader = {webroot}\MachII\framework\AppLoader.cfc
ContactManager.model.ContactManager =
{webroot}\ContactManager\model\ContactManager.cfc
Hope this clears things up for folks...chris
>-----Original Message-----
>From: Mike Kear [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, August 13, 2003 10:48 AM
>To: CF-Talk
>Subject: RE: Mach II 1.0 released
>
>I'm puzzled too, Tony. All I've done is open the MachII_1_0_0.zip file and
>extract it to c:\inetpub\wwwroot. It happily installed all the files into
>folders under c:\inetput\wwwroot\machii.
>
>Dave Carabetta said I also had to unpack the contactmanager app, but there
>is already a contactmanager folder under the Machii folder. Is this not
>the
>sample app?
>
>After I unzipped the machii file, I navigated to http://localhost/machii
>and
>that's where I got the error message. When I went to
>http://localhost/machii/contactmanager I got another message saying
>something couldn't be found.
>
>I have to say that just looking at all these files doesn't help much.
>There
>are now 56 files under the /machii folder, and while I haven't actually
>looked at all of them, none I've found seem to do anything themselves, they
>all seem to call something else. I can't see where any data is being
>stored, and what all these files do is not at all obvious to me.
>
>I guess this machii thing is going to be beyond me until I can win lotto
>and
>afford to travel to a training session in the USA.
>
>It's certainly not like fusebox, where the functionality of everything is
>pretty obvious and it's easy to follow what's doing what even for
>non-fusebox people.
>
>
>
>Cheers,
>Michael Kear
>Windsor, NSW, Australia
>AFP Webworks.
>
>
>
>
>-----Original Message-----
>From: Tony Weeg [mailto:[EMAIL PROTECTED]
>Sent: Thursday, 14 August 2003 3:20 AM
>To: CF-Talk
>Subject: RE: Mach II 1.0 released
>
>I don't have a mapping in my cfadministrator?
>
>what am I missing? is there some sort of install this this way freakin
>doc somewhere?
>
>tony weeg
>uncertified advanced cold fusion developer
>tony at navtrak dot net
>www.navtrak.net
>office 410.548.2337
>fax 410.860.2337
>
>
>-----Original Message-----
>From: Dave Carabetta [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, August 13, 2003 1:16 PM
>To: CF-Talk
>Subject: RE: Mach II 1.0 released
>
>
>>I had the same problem as Tony Weeg - with exactly the same error
>>message (except mine said the error was on line 14 not 11)
>>
>>I looked at the mappings set up in CFadminstrator and it had set up a
>>/machii mapping to c:\inetpub\wwwroot\machii\contactmanager
>>
>>So I manually changed the mapping to C:\Inetpub\wwwroot\MachII and
>the
>>problem went away.
>>
>>That's the good news.
>>
>>The bad news is it was replaced by another error message telling me it
>>couldn't find something else. (specifically: The cause of this
>>exception
>>was: java.io.FileNotFoundException:
>>C:\Inetpub\wwwroot\MachII\config\mach-ii.xml (The system cannot find
>the
>>path specified).
>>
>>Is there a doc somewhere that sys where everything ought to be for a
>>default
>>installation?
>>
>
>The framework itself can't be run on its own (at least, as far as I can
>tell). It has to be run as part of an example. Download the
>ContactManager,
>unzip it to your root, and then navigate to the index.cfm file in your
>browser. It all worked easily for me.
>
>However, my problem with it is that the perfmance of the framework isn't
>
>very good. But that's another issue altogether.
>
>Regards,
>Dave.
>
>_________________________________________________________________
>MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*.
>http://join.msn.com/?page=features/virus
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription:
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Signup for the Fusion Authority news alert and keep up with the latest news in
ColdFusion and related topics.
http://www.fusionauthority.com/signup.cfm
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
