I have now committed the changes necessary to use the translated attribute value instead of the raw value as the key in the mapped configurations.
I also adjusted the documentation accordingly. I was wondering if it would make sense to add a new subsection to the "Configurations" documentation page about mapped configurations (with an example) as this feature is only mentioned in a few sentences. What do others think? --knut On Fri, 28 Jan 2005 13:21:41 -0500, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > Just a thought for discussion. I'm looking at Knut's code for > converting configurations to maps. One thing that nags me is that it > uses the raw attribute value as the key. > > Not sure that is best; I think the translated value for that attribute > is the right thing. > > Only example that jumps to mind is if the translator is qualfiied id. > In that case, the attribute value may be "foo" but the qualified id > will be "mymodule.foo" ... that's what will be assigned to an object > property, and it makes sense that the Map be keyed on "mymodule.foo" > not just "foo". > > -- > Howard M. Lewis Ship > Independent J2EE / Open-Source Java Consultant > Creator, Jakarta Tapestry > Creator, Jakarta HiveMind > > Professional Tapestry training, mentoring, support > and project work. http://howardlewisship.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
