David Ross wrote:
Marlon,
I just replied over on the CS forums, but I'll repost it here as well.
We typically don't use ColdSpring to create "value objects", which is
what your "user__bean" is in this context. It all depends on how you
build your apps... I typically use ColdSpring to configure and wire
together my services/daos/gateways/utils/etc, but the actual creation of
my value objects is done either by some external entity (like the
controller layer) or in the DAO layer. Even though we support
"prototypes" (meaning <bean/>'s with singleton="false"), it doesn't mean
we use them very often. In this particular case, making your DAO obtain
new "user__bean's" from ColdSpring would tie your DAO (part of your
Model) to ColdSpring (just a framework), which is not a great thing to
do. Your Model should be completely unaware of the existence of
ColdSpring.
Hope that helps...
-Dave
I usually have my service/manager class pass in an init() bean or
transfer object. I usually don't want to give my DAOs the
responsibility of creating my bean/transfer object.
I agree with Dave that you would be tying CS to your model unnecessarily
- although the thought of using CS to manage my beans crossed my mind
briefly at one point.
Best,
.Peter
--
Peter J. Farrell :: Maestro Publishing
http://blog.maestropublishing.com
Rooibos Generator - Version 2.1
Create boilerplate beans and transfer objects for ColdFusion for free!
http://rooibos.maestropublishing.com/
Member Team Mach-II
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
