RE: Lazy concatenation of strings and Ant

How would sfStart() in this example be any different than sfDeploy()?  What I'm having a hard time understanding is how any case which would speak for sfStart() would be harmed by having the properties read in sfDeploy().  Considering that the majority of components read their configuration in sfDeploy(), it would seem that sfDeploy() is the ideal place for this component to do its work.  Myself, I'd have to see a case where reading the properties in sfDeploy() would be the wrong thing to do.  I can't think of any off hand - but that's not saying much :)

> -----Original Message-----
> From: smartfrog-developer-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org [mailto:smartfrog-
> developer-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of Steve Loughran 
> 
> Guijarro, Julio wrote:
> > Hi Hal,
> >
> >
> >
> > The ANT component did not check for attribute values using SmartFrog
> > reference and it was adding then directly to the Ant tasks without
> > trying to resolve them first and that is the reason for the class cast
> > exception. I have fixed the ANT component in CVS.
> >
> >
> >
> > In your example there was another potential problem because the
> > LoadPropertyFile component was creating the sf attributes during sfStart
> > instead of sfDeploy. I have also fixed this component in CVS and it now
> > gets ready to be used/queried during sfDeploy.
> >
> >
> 
> That assumes that sfDeploy is the right place for the property file to
> be loaded. I could construct use cases in which sfStart() was the right
> place to do the work, such as any workflow-like situation in which one
> thing generated a property file that another thing then read. It should
> really be a switch readOnDeploy or something.,
> 
> -S. 



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642