Hello, I've been looking at Model Glue 3 for the first time ever today and its been a little while since I've looked at Model Glue 2 as well, so its been a fun day of reading and tinkering.
The tinkering involved switching out Model Glue 2 from one of our base installations and replacing it with Model Glue 3. The first configuration issue I battered my head against was the change to the TransferAdapter that means that it requires a transfer bean passing to it. That was kind of "fun" as, for whatever reason we have/had multiple references to "ormAdapter.Transfer" beans and I could seem to configure them correctly. (I suspect this will bite me later when I access the application from a different context) The next bit of tinkering involved dropping in a small Scaffolded MG:U application. The application basically barfed on the first call. The reason being was that it was attempting to save generated views in a location that did not exist. The reason it didn't exist was because it was not the location that the generatedViewMapping was pointing to. The generatedViewMapping was set as "/sitename/appstore/applicationmgr/views/generated". The path that the scaffold manager was trying to write to seemed to be under the web root, which is not where this mapping was pointing. After a bunch of digging and cfdump/cfaborting I eventually discovered that "variables._MGConfig.scaffoldCFPath" in the ScaffoldManager was set to "//sitename/appstore/applicationmgr/views/generated". Note the double "/" at the front there. This led me into the ModelGlueConfiguration cfc and the getFullGeneratedViewMapping() function. This function returns the generated view mapping plus the application mapping. I made a mistake that threw me and tried to add an applicationmapping setting in the wrong coldspring file (one that I thought this sub application inherited off). Argghh... I'm babbling - sorry. Basically it comes down to this.. While I appreciate that generated views should be in a folder under the application path, why does the configuration only do this for the generated view mapping? Surely the configurationPath and scaffoldPath should also be relative to the application mapping as well? Its kind of confusing, especially when you're "upgrading" an existing MG:U application to MG:G for this to have change in only one property and to have changed at all. Regards and sorry for the verbal diarrhoea. Stephen PS. I'll add a couple of notes to the upgrade from 2.0 page on the wiki about these -- Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog 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
