Alagad Ally - Web Development Task Force

I am part owner of another web company, which shall remain unnamed.  A few years ago I (and a couple others) wrote their current web application.  Initially the application was sufficient, but over time we’ve run into some limitations …

Unfortunately, cf.Objective 2010 was not in the cards for me this year, and I apparently missed out on many marvelous sessions. I would have been particularly interested to attend Dan Wilson’s “Speedy Gonzales Guide to Model-Glue” session, as Model-Glue 3.2 …

A question came up on the Model-Glue mailing list today regarding forcing regeneration of ColdSpring remote proxies
when reinitializing a Model-Glue application. As the solution to this
is not obvious, I thought it would be good fodder for a blog post:
The first thing to understand about this is the fact that the
configuration for remote proxies in ColdSpring includes a
“beanFactoryName” property, and this property is used as the key in the
application scope that will be used when generating the remote proxy
components. In other words, if our ColdSpring config defines the
beanFactoryName property as “beanfactory”, then ColdSpring is going to
look for a bean factory stored in application.beanfactory — if it does
not exist, it will be created.

Its no secret that at Alagad we like Model-Gue.  We frequently use the framework on projects and several of us have contributed to the project over the last few years.  Some of us were even privy to Model-Glue before it actaully made it out into the world.

Joe has dcided that he would like to have more community input into the roadmap of Model-Glue, as well as get a better understanding of how Model-Glue is being used, and which features are most valuable to the developers who use it.  Help mold the path of Model-Glue by taking some time to fill out the survey mentioned here. 

This is your chance to be heard, don’t pass up the opportunity!

The ModelGlue list had an interesting question come up this week. "Interesting questions" on lists are the primary source of blog fodder for me, mostly because I find myself writing responses that are worth reformatting a bit and posting to the blog… and such, honestly, is the case here. The individual in question was asking whether using the new beans="" attribute in ModelGlue:Gesture controllers would couple your application too tightly to the framework and therefore shouldn’t be used. Before I get into the answer, however, a brief aside:

For those not-in-the-know, adding the beans="" attribute to the cfcomponent tag of an application controller in MG:G, and providing a comma-delimited list of bean IDs from the ColdSpring file (you are using ColdSpring, right?) will automatically pull those beans from ColdSpring and compose them at variables.beans.beanName.

Example: