LiveDocs Comments - wtg - public - machiidevguide - index.html

wtg/public/machiidevguide/index.html

SeanCorfield — 2006-08-12T14:03:19

Whilst Mach II does not support multiple XML file, you can have multiple Mach II applications, each with its own XML file, that all share the same ColdFusion application scope (and session scope, so you can have single sign-on).

wtg/public/machiidevguide/index.html

2006-08-10T15:20:17

I am wanting to make seperate xml files for different projects. Is there something that I can alter or change to do so? So one tool has it's own set of views, listeners, and event-handlers.

wtg/public/machiidevguide/index.html

SeanCorfield — 2005-03-30T09:02:51

Yes, Mach II works flawlessly on ColdFusion MX 7. About a quarter of the fifty or so applications on macromedia.com are built with Mach II and macromedia.com has been running CFMX 7 since early February.

wtg/public/machiidevguide/index.html

jaz_wd — 2005-03-30T08:35:41

I need to know if Mach-II Works with CFMX 7.0.

wtg/public/machiidevguide/index.html

SeanCorfield — 2005-01-10T07:39:52

Andrew,

Although you will need a mapping to include the core mach-ii.cfm file (unless you copy it locally into your application), the more important piece of setup is to use a custom tag path so that the Mach II CFCs can be found.
ColdFusion uses custom tag paths to look for both custom tags and for components.

wtg/public/machiidevguide/index.html

Andrew Mercer — 2005-01-10T06:51:17

Hi Sean,

In section 'Mach II Core Files' it has the files can be installed to the CF document root or in a Custom Tag Path. Should that actually be a mapped path (ColdFusion Mappings)?

wtg/public/machiidevguide/index.html

SeanCorfield — 2004-02-18T11:38:59

Re: cflock - the 1.0.9 release uses named locks around shared scope variables in mach-ii.cfm.
That ensures that all of the configure() methods are thread-safe (and therefore do not need locks).
If a listener, event filter or plugin method updates variables scope data (which is implicitly in application scope), then you would need to use a (named) lock to ensure thread safety.

wtg/public/machiidevguide/index.html

austinnichols101 — 2004-02-18T09:59:26

Would it make any sense to use a 'cflock name=' for locking the shared-scope variables in machii? It would seem that by using name= that you wouldn't have to lock the application scope as a whole, for example.