I'm still pretty sure that ColdSpring has never supported passing complex
variables as properties so I'm somewhat confused as to how this would have
worked before. I know that using the latest version of ColdSpring it
definitely doesn't work and I can't imagine why Chris or Dave would have
removed that functionality if it was there before. As it stands you'll have
to modify your code to pass a struct of simple variables as your properties.
Once you do that it should work.
On 8/13/07, Ronaldo Junior <[EMAIL PROTECTED]> wrote:
>
> Hi Brian,
>
> Sorry for my delay in getting back to you on this.
> I had a better look into what I was assuming was just a variable name
> containing dot and it was not really a simple variable name.
> It really was a structure that it's been passed to coldspring's
> setProperty method and it used to work but now it stopped.
> I made some changes to our code base, now it's passing the right thing and
> it's fixed.
>
> I have another question.
> If I have the following settings into my service.xml file
>
> <constructor-arg name="test">
> <list>
> <value>${environment.test1}</value>
> <value>${environment.test2}</value>
> </list>
> </constructor-arg>
>
> Assuming test is a real constructor argument and both environment.test1and
> environment.test2 are real properties Should this work and inject the
> right values into my component?
> Because at the moment it's injecting ${ environment.test1}, not the
> property content.
> Was this supposed to work like for simple value?
>
> Thanks
> Ronaldo
>
>
>
