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.test1 and
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
On 8/8/07, Brian Kotek <[EMAIL PROTECTED]> wrote:
>
> I'm still somewhat confused, is this an issue with the Mach-II ColdSpring
> plugin? Because on the latest version of of the BeanProperty file (1.20) I
> can feed in a property with a dot in it like <cfset myproperties['
> someprop.withadot'] = "foo" /> and it works fine.
>
> On 8/7/07, Ronaldo Junior <[EMAIL PROTECTED] > wrote:
> >
> > Hi Brain,
> >
> > The property name has a dot.
> > It used to work fine but it seems like since version 1.19 or so it
> > stopped working.
> >
> > This property name is just like ANT properties.
> >
> > Eg.: Imagine this property tag in your ant build file, the name in bold
> > is what I have been using.
> >
> > <property name="environment.machine" value="TEST" />
> >
> > Coldspring used to accept property names containing dots but it does not
> > work any more.
> >
> >
> >
> >
> >
> > On 8/7/07, Ronaldo Junior < [EMAIL PROTECTED]> wrote:
> > >
> > > Hi Brian,
> > >
> > > Thanks for your answer but I think I have not been clear on explaining
> > > my situation.
> > >
> > > I am not trying to add complex objects to my properties; they are all
> > > simple strings; their names are composite names.
> > >
> > > Eg.:
> > > server.name = "servername"
> > > environment.machine = "machinename"
> > >
> > > My problem is that the property's names contain DOT like the ones in
> > > bold above.
> > > This used to work just fine but now with the new version in the CVS it
> > > stopped working.
> > >
> > > It's working for me now because I did almost what you suggested but
> > > instead of going into the code and doing my own changes, I just grabbed an
> > > older version of BeanProperty component from the CVS and things seem to
> > > work
> > > just fine.
> > > For instance, the version I am using now is 1.17 of this file.
> > >
> > > I just changed this specific file and everything seems to work so if
> > > you take a look at the current file and the one I am using(version
> > > 1.17) you will see that the parseValue method is slightly different
> > > from one another.
> > >
> > > Ronaldo
> > >
> > >
> > >
> > > On 8/7/07, Brian Kotek < [EMAIL PROTECTED]> wrote:
> > > >
> > > > Properties only accept simple values (a string). It won't resolve
> > > > complex types like structures which is what you appear to be trying to
> > > > do.
> > > > So assuming that is the problem, you'll have to change the way you're
> > > > passing your properties in so that they are just simple values. You can
> > > > also
> > > > petition Chris or Dave to add this as an enhancement, or try your hand
> > > > at
> > > > modifying the code to support structures and submit it as a patch.
> > > >
> > > > On 8/5/07, Ronaldo Junior < [EMAIL PROTECTED] > wrote:
> > > > >
> > > > > Hi All,
> > > > >
> > > > > I came across this problem when I updated my coldspring to the
> > > > > lastest one from CVS in order to have the import feature.
> > > > > I have been running the 1.0.0 final release and no such a problem
> > > > > occurs.
> > > > >
> > > > > Digging a little into the code I found out that the component
> > > > > BeanProperty, method "parseValue" that parses the tag <value> is not
> > > > > working
> > > > > properly when the property contains DOT like PROPERTY.NAME.
> > > > > The system I am working on have a considerable amount of such
> > > > > properties in property scope and it is reporting the following
> > > > > message.
> > > > >
> > > > > "Invalid Path To Config:The path ${environment.reactorConfig} does
> > > > > not exist."
> > > > >
> > > > > Is anyone having the same problem?
> > > > > Does anyone know when the fix for it will come out?
> > > > >
> > > > > Cheers
> > > > > Ronaldo Junior
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Ronaldo da Silva Gomes Junior
> > >
> >
> >
> >
> > --
> > Ronaldo da Silva Gomes Junior
> >
>
>
--
Ronaldo da Silva Gomes Junior
