No, it's not a one liner unfortunately. I've gone through the MG code
and references to CFCs are all though it like this
<cfset variables.beanMaker = createObject("component",
"ModelGlue.Util.CollectionBeanMaker").init(variables.state) />
The "ModelGlue" path, dependent apon a mapping, appears in numerous
places. If I want a different mapping I have to run a global search
and replace and ensure I don't accidentally mess up other code in
which the word ModelGlue appears. While it is feasible, it's still a
pain.
On 5/21/06, Jochem van Dieten <[EMAIL PROTECTED]> wrote:
> James Holmes wrote:
> > I inquired about this a while ago. A mapping is necessary if MG is to
> > be used as-is on a shared server, meaning that everyone needs to share
> > the same version of MG (in the same mapping). This would make
> > upgrading a chore.
> >
> > You could modify MG to use a different path (and therefore your own,
> > unique mapping) but then you have to modify the whole MG codebase
> > every time an upgrade is released.
>
> Which is a one-line fix. Would you consider that a significant
> part of the upgrade cycle of a core component of your application?
>
> Jochem
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:241069
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
