Generic getters and setters are one way to mitigate this. Instead of
user.getuserid()
user.getemail() etc.
You have
user.get('userid')
user.get('email')
etc.
You just need one get and one set method for each class.
I think there is a gotcha relating to Flex somehow. Peter Bell's blog has
some information on this: http://www.pbell.com
-- Josh
----- Original Message -----
From: "Joseph Frank" <[EMAIL PROTECTED]>
To: "CF-Talk" <[email protected]>
Sent: Wednesday, April 11, 2007 11:06 AM
Subject: setters/getters - scalability issues?
> Apparently, each method in a CFC turns into its own compiled Java class in
> addition to the CFC itself. If I generate setter/getter methods for each
> of my class properties, wouldn't that be an issue in terms of scalability?
> For example, instantiating this CFC into Session scope, instead of what
> seems to be a single class per application user, now I have 30 class
> references per user.
>
> Any thoughts?
>
> Joe
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
ColdFusion MX7 and Flex 2
Build sales & marketing dashboard RIAâs for your business. Upgrade now
http://www.adobe.com/products/coldfusion/flex2?sdid=RVJT
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:275034
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
