I just posted my notes from the keynote this morning at my blog,
www.codfusion.com The keynote covered a lot of new features coming in the
next release of Coldfusion.
John Mason
[EMAIL PROTECTED]
770.337.8363
www.FusionLink.com - ColdFusion and Flex hosting
Now offering VPS Plans running with
Implicit getters/setters
The cfproperty will generate the implicit getters and setters on the
backend to save you from writing the code.
nice! Was overriding mentioned for these?
DK
On Wed, Jun 18, 2008 at 10:28 AM, John Mason [EMAIL PROTECTED] wrote:
I just posted my notes from the keynote
immediately and delete this message and all
copies and backups thereof.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas Knudsen
Sent: Wednesday, June 18, 2008 10:39 AM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] CFUnited Report - Adobe Keynote
I also saw that CF will now be FREE for academic use, including
Enterprise. That's fantastic. Very very cool.
-Cameron
On Wed, Jun 18, 2008 at 10:39 AM, Douglas Knudsen
[EMAIL PROTECTED] wrote:
Implicit getters/setters
The cfproperty will generate the implicit getters and setters on the
-Original Message-
From: John Mason [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 18, 2008 10:55 AM
To: discussion@acfug.org
Subject: RE: [ACFUG Discuss] CFUnited Report - Adobe Keynote
Yes, so if you have your own getters/setters then CF will use those. If
they
are not present
Which of course sucks if you want encapsulation and limits on the
setters/getters based on authorization. Is this controllable in some
manner?
-dhs
Dean H. Saxe, CISSP, CEH
[EMAIL PROTECTED]
Free speech exercised both individually and through a free press, is
a necessity in any country
I should say beyond having to implement your own setters/getters...
which still doesn't really solve the problem of properties which you
explicitly do not want setters/getters on unless you throw exceptions
on the unimplemented ones. Yuck.
-dhs
Dean H. Saxe, CISSP, CEH
[EMAIL PROTECTED]
These sorts of questions are why people participate in alpha/beta
programs. These are all points which should be brought up and aired
out WAY before the final bits ship. Some thoughts come to mind
1) Add access attributes to cfproperty for public/private
2) Add roles attribute for
What I would want to is annotate the properties to say whether the
getter/setter should be autogenerated, that way it leaves control to
the developer. I like the idea of the addition of a roles check for
authorization to call specific setters/getters.
Also, is the autogenerated
On Wed, Jun 18, 2008 at 3:10 PM, Dean H. Saxe
[EMAIL PROTECTED] wrote:
What I would want to is annotate the properties to say whether the
getter/setter should be autogenerated, that way it leaves control to the
developer.
If you don't want it autogenerated, just call it private. It's not
I can see a reason to have auto generated getters and setters based on a
database table (and possibly typed) but you can effectivley do this now with
a missing method handler...
I'm guessing this is based on a table somewhere?
On Wed, Jun 18, 2008 at 3:26 PM, Cameron Childress [EMAIL PROTECTED]
No, if it follows the pattern seen in AS3, it would be something like
this... Given a property definition like this:
cfcomponent
cfproperty name=firstname type=String access=public roles=Admin,User /
[]
/cfcomponent
You'd get two implicit getters/setters with the signature
ColdFusion 8 Enterprise hosting
FREE Subversion hosting
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cameron
Childress
Sent: Wednesday, June 18, 2008 6:34 PM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] CFUnited Report - Adobe Keynote
13 matches
Mail list logo
