PIMP!!!!! :-D

I made the change and it is working as advertised. :-D

---
John C. Bland II
http://www.johncblandii.com
http://www.johnandseason.com
http://www.twitter.com/johncblandii
---
Suggested sites:
http://www.lifthimhigh.com - "Christian Products for Those Bold Enough to
Wear Them"
http://www.sportsmatchmaker.com - "What are you doing today?"


On Thu, Oct 8, 2009 at 12:42 PM, Dan Wilson <[email protected]> wrote:

> (We blogged the answer:
> http://www.model-glue.com/blog/index.cfm/2009/10/8/Ask-ModelGlue-Beans-Scope)
>
>
> Hi , John, that looks pretty good. You are definitely on the right track
> with your event type work. Your question is actually a very timely one and
> gives us an opportunity to share a new feature of Model-Glue 3. Since you
> are interested in short cuts and in using MG3 most effectively, let's talk
> about the newly added Beans scope.
>
> In your code sample, you defined a configuration bean in ColdSpring, always
> a good thing, and retrieved it from ColdSpring with the syntax
> getModelGlue().getBean("urlConfig").
>
> Nothing is wrong with that syntax at all, and your code will work fine.
> However, there is an even easier way to get beans from ColdSpring. MG3
> introduces the concept of the Beans scope that is not only easier, but it
> also leaves good documentation of your application as well.
>
> Consider this code:
> <cffunction name="SetPageConfigs" access="public" returntype="void"output=
> "false">
>    <cfset arguments.event.setValue("urlConfig", getModelGlue().getBean(
> "urlConfig")) />
> </cffunction>
>
> The urlConfig object is retrieved from ColdSpring through the
> getModelGlue().getBean() declaration. What is nice about this is it makes
> accessing ColdSpring managed objects very easy. However, it sort of makes it
> difficult to find all the the Coldspring managed beans in a specific
> controller. Using Find tools to scan source code for references is not
> really the very best thing because other developer may have chosen a name
> that isn't obvious or has been abstracted for some reason. Model-Glue 3
> introduces the notion of a 'beans' scope. The Beans scope is a
> controller-wide scope containing all the ColdSpring managed beans for a
> specific controller. Here is a short sample:
>
> <cfcomponent extends="ModelGlue.gesture.controller.Controller" output=
> "false"
>          beans="urlConfig,UserService">
>
>    <cffunction name="doSetUp" output="false" access="public" returntype=
> "void" hint="I perform global setup stuff for each request">
>       <cfargument name="event" type="any">
>       <cfset arguments.event.setValue("urlConfig", beans.urlConfig ) />
>    </cffunction>
> ...
>
> See the beans attribute of the cfcomponent tag? This is a comma separated
> list of all the ColdSpring managed beans we need in this controller. Inside
> the doSetup() method, we use the prefix 'beans' to get at the specific
> object:
> beans.xxxxx
>
> One nice effect of this technique is less typing on the keyboard.
>
> More importantly, we now have a bit of *auto-documentation* on exactly
> which ColdSpring managed beans are used by this controller. This
> documentation is at the very top of the file. Now, when you maintain your
> code, or code from other developers, you can simply read the beans attribute
> in your controller to find out which beans are in use, rather than scanning
> or reading lots of code for that information. Nice huh?
>
> Model-Glue is all about building applications quicker and reducing
> maintenance costs and I'm sure you'll agree the Beans scope makes sense on
> both fronts.
>
> Keep sniffing the 'Glue
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to