Misha Vodsedalek wrote: > "Kevin Thorley" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] >> I was just typing the same response :) The issue described in XCF-2297, >> and the associated fix, only applied to loadable localization packs. I >> did not make any changes related to the way that tapestry loads >> localization files that are part of the source (as is the case here). >> However, I also can't guarantee that the loadable localization code >> doesn't somehow break the regular tapestry message resolution (I doubt >> it, but its possible). >> >> We should open a new issue for this. If it is found to be related to >> XCF-2297, we can always link it in Jira >> >> Kevin >> > > I don't see how tapestry could be impacted by your code that I believe gets > executed only when there is a message store (a jar file) for the selected > language. BTW - I could create a localization package from the Italian > *.properties files - using the sipxconfig_it.jar file and excluding the > Italian *.properties files from the sipxconfig.war file should yeild the > expected results (that is English strings in the GUI when Italian strings > are missing). > > Misha >
By default, Tapestry only loads localization property files from the .war file. I had to make add a new message source handler that first looks in the jar, so its possible that there is a bug here that is preventing tapestry from correctly handling messages in the .war. Alberto, by any chance do you have an Italian localization pack installed in addition to the property files that you have in the src dir? Kevin _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
