Damian Krzeminski wrote: > Ernest Rott wrote: >> Hello, >> >> For components without .jwc or .page corresponding file, so called >> specless components, the localization will fail even if the appropriate >> .properties files are located in the same folder as .html component file. >> >> I found a solution to fix this strange behavior. We put all .properties >> files for a component in the same package folder as associated >> component Java class. At first side my idea appears weird but it's the >> same solution adopted for Tapestry 5. See >> http://tapestry.apache.org/tapestry5/guide/localization.html >> >> In this manner the localization for specless components will work like a >> charm. >> > > Moving this to sipx-dev list... >
In 4.0 we should probably stick to workaround Huijun found. In mainline I am OK with moving the properties to 'src' directory. Especially if it turns out that fixing or extending Tapestry to handle this is not trivial. Some things that need to be checked: - "java-less" components: We have a few components which do not have special java classes (based directly on BaseComponent). I think that they will need .jwc in any case, but should we move those .jwc's 'src' as well? - downloadable language bundles: Personally I'd like all sipXconfig strings just to be checked in (that would leave language bundles limited to voicemail stuff), but it's probably not going to happen, so we do need to make sure we still support them properly. Opinions? D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
