Is there no way to provide two different TranslatorSources  and a symbol for
compatibility mode? The users would decide which version of TranslatorSource
to use by providing a value for that symbol.

On Thu, Apr 29, 2010 at 6:11 PM, <[email protected]> wrote:

>   Release 5.2.0
>
> +* TranslatorSource
> +
> +  The configuration type for TranslatorSource has changed in an
> <<incompatible>> way: from
> +  an unordered collection to a mapped collection; this is to support
> overrides. This will break
> +  existing module classes that contribute to the TranslatorSource service
> configuration.
>


-- 
Best regards,

Igor Drobiazko
http://tapestry5.de/blog

Reply via email to