Thanks to all who replied to my posting. I'd like to summarise my reply:
salvatore wrote:
I suggest reading hal helms articles about strong and dinamic typing
Yes, tried to read that. Bit over my head but I'll try again.
Mihai wrote:
The luxury of different dev and live servers is a poor
Dave thanks for the information. Based on your feedback and reading
the post on Ben's blog I seem to have come to the following conclusion.
"The use of 'Duck Typing' w/a CFC is 'out' should the CFC ever be
needed for use by a Flex application. "
Do you (and anyone else knowledgeable on Flex
On 3/21/06, Jason Daiger [EMAIL PROTECTED] wrote:
Dave thanks for the information. Based on your feedback and reading the
post on Ben's blog I seem to have come to the following conclusion.
The use of 'Duck Typing' w/a CFC is 'out' should the CFC ever be needed
for use by a Flex
On 3/21/06, Jason Daiger [EMAIL PROTECTED] wrote:
Dave thanks for the information. Based on your feedback and reading the
post on Ben's blog I seem to have come to the following conclusion.
The use of 'Duck Typing' w/a CFC is 'out' should the CFC ever be needed
for use by a Flex
Dave,
Is this true even if you go through a service layer? Also, can you
provide any links or references on this issue w/ Flex2? I'm not
designing in Flex 2 at the moment but our long range plan for the UI is
to migrate various pieces of the app to Flex2. So since the app is in
development
On 3/20/06, Jason Daiger [EMAIL PROTECTED] wrote:
Dave,
Is this true even if you go through a service layer? Also, can you provide
any links or references on this issue w/ Flex2? I'm not designing in Flex 2
at the moment but our long range plan for the UI is to migrate various
pieces of
On 3/20/06, Nando [EMAIL PROTECTED] wrote:
And are we still speaking about using a fully qualified *returntype* if
your thinking about using Flex? Or are you saying the path used to
instantiate the object would need to be fully qualified if you're going
to use Flex?My understanding is
I didn't suggest setting the type/returntype to any; I just
suggested using an unqualified component name (User) instead of a
fully-qualified component name (com.company.app1.User). It should
only be an issue if you have two CFCs of the same name in different
packages. That seems like a fair
On 3/17/06, Cliff Meyers [EMAIL PROTECTED] wrote:
I didn't suggest setting the type/returntype to any; I just
suggested using an unqualified component name (User) instead of a
fully-qualified component name (com.company.app1.User). It should
only be an issue if you have two CFCs of the same
On Thursday 16 March 2006 10:09, dickbob wrote:
What are the benefits? All seems to work okay without them.
But it'll make your cfcdoc output look nasty, and doesn't give anyone else (or
you) a clue as to what is returned.
Do I need to give the full pathname to the component? Why?
You
Hi Tom,
Thanks for your comments...
How do I reconcile the fact that the pathname must be a constant value with
the path being different between the dev and live environments?
You mean you have objects like
com.wibble.fo.bar
on live but something different in development ? Why ?
Not all
I suggest reading hal helms articles about strong and dinamic typing
regards
salvatore
- Original Message -
From: dickbob [EMAIL PROTECTED]
To: CFCDev@cfczone.org
Sent: Thursday, March 16, 2006 11:09 AM
Subject: [CFCDev] How to use returntype correctly
Hi,
I've been using cfc's for
Hmmm ...
Hal Helms, who's a Java programmer as well as a ColdFusion programmer
and seems to know and understand the benefits of static typing in Java
has been writing and speaking a lot about this topic lately.
You can find his newsletter at halhelms.com and his podcasts at
The luxury of different dev and live servers is a poor excuse for not downloading the coldfusion developer edition and installing it on your local machine as development server.
Best regards,
Mihai
On Thu, 2006-03-16 at 10:43 +, dickbob wrote:
Not all of us have the luxury of a
: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of dickbob
Sent: Thursday, March 16, 2006 5:43 AM
To: CFCDev@cfczone.org
Subject: Re: [CFCDev] How to use returntype correctly
Hi Tom,
Thanks for your comments...
How do I reconcile the fact that the pathname must be a constant
value
@cfczone.org
Subject: Re: [CFCDev] How to use returntype correctly
Hi Tom,
Thanks for your comments...
How do I reconcile the fact that the pathname must be a constant
value with the path being different between the dev and live
environments?
You mean you have objects like
On Thursday 16 March 2006 13:07, Peter Bell wrote:
dependency injection engine like ColdSpring should allow you to do this
kind of conditional metadata at runtime (someone with ColdSpring experience
/me nods
We use Spring in our Java projects for exactly that purpose.
--
Tom Chiverton
I much prefer being able to specify the type of the Component I am passing, and this is primarily for documentation purposes.Yes you can work fine by setting it to 'any', and then living with developer guidlines to ensure the right object is passed through, but I personally find this kinda cludgy.
dickbob wrote:
Not all of us have the luxury of a different dev and live server so I
have...
com.dev.wibble.fo.bar
...and...
com.live.wibble.fo.bar
...for the two different code streams.
Dickbob
What you need, are two instances, one for your dev environment, and one
for your live. See
Union
(916) 569-5409 Office
(916) 569-2024 Fax
www.schools.org
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of dickbob
Sent: Thursday, March 16, 2006 2:43 AM
To: CFCDev@cfczone.org
Subject: Re: [CFCDev] How to use returntype correctly
Hi Tom,
Thanks
20 matches
Mail list logo
