When I first started using MG, I mostly did first method exclusively, using generic messages a lot of the time. Now that I write my own services, I tend to use the second method. As stated, I seem to get a clearer picture of what's going on for an event in one place. I can see what I'm naming variables, etc. But as Dan said, it depends on the situation.
byron On Jan 18, 12:21 pm, Mike Lowry <[email protected]> wrote: > I've been using the first method for a lot of the cases, but what I'm > seeing is that on events that require a lot of different data, it is > getting cumbersome to change things or get the big picture for a > particular event. I end up having 10 files open for 1 event: > controller files, several modelGlue.xml files, plus several model > objects (services or decorators) and of course the view or views. > > Also with the single concept per message you have to remember what > exactly is being loaded into the event, so for example the needUser > message, is it loading a transfer object? a query? was it named > 'userObj', or 'user' etc. The 2nd way you'd be able to see all of the > values that are being set in the event in one place. Of course this > will come at the price of duplication if those values are used in > other events. > > Mike Lowry -- 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
