Everett,
You can use Application.cfc's onRequest() function to always
<cfinclude template="./index.cfm" />, which will then include
modelglue.cfm and your request will run just fine.
Doug,
Are you saying there are issues with per-app mappings in general, or
just with MG apps? The only issue I've ever seen people have is the
confusion over what the key names have to be in this.mappings. We're
using per-app mappings on one of our projects and everything's
working just fine... just use this kind of syntax:
<cfset this.mappings["/modelglue"] = "/path/to/ModelGlue">
Works awesome and it does in fact override mappings set at the server
level.
J
On Nov 13, 2008, at 11:58 AM, Doug Hughes wrote:
> I recall that there are problems with per-app mappings. Your
> mileage may vary.
>
>
> On Thu, Nov 13, 2008 at 12:53 PM, Al <[EMAIL PROTECTED]> wrote:
>
> A possible solution is to use per-application mappings. That way, for
> applications I'm currently working on, I can setup a mapping
> ("ModelGlue") that points to E:\ModelGlue2 instead of E:\ModelGlue,
> leaving the server-level mapping pointing to the old version. Then,
> when we've all got them upgraded (probably six months after MG3's
> release) the server-level mapping can be changed.
>
> Trouble is, for per-application mappings, I need to use
> Application.cfc. Out of the box, MG uses Application.cfm.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "model-glue" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/model-glue?hl=en
For more about Model-Glue, check http://www.model-glue.com .
-~----------~----~----~----~------~----~------~--~---
