It is mentioned in the Reactor docs that the <field> tag can be used within your object definitions to pretty up ugly column names such as txt_lastname or strCity, but it should also be noted it can be used to diferentiate between two tables which both have fields with the same name.

for example, if all my tables have a modified date timestamp

Then, when I am doing a join later, I can reference the modified dates correctly.

This may be old news, but did everyone know you can include ModelGlue.xml file within your main modelglue.xml files. The framework has provided an tag within the modelglue config file. you can include as many XML files as you need as long as they are formatted correctly.

The include tag goes after the opening <modelglue> tag and before the first <controller> tag

then you can group the event handlers into multiple files to keep them organized in a logical way.

example:

I have really been loving the generic ORM stuff that is part of ModelGlue 2.0. I had been doing way to much work to stuff the objects we needed into the viewstate. Now I have been able to remove countless listeners and broadcasts I was using to get various objects when needed.
Now a generic read takes care of that.

The basic functionality of the generic events are documented at http://docs.model-glue.com so I wont get into how to use them, but one thing that isn't documented is how to handle updates to multiple unrelated objects in the same form post( event-handler)

Here is how I am doing it, It works like a charm for quick prototyping,as far as I am concerned.

Lets say I have 2 objects, Cinders and Ashes. I am collecting this data on the same form and I need to handle the validation and update the results. I need two generic commit message broadcasts

My form lives at an event called "CindersAndAshes.form" and submits to an event called