Help Desk Ticket Reference: https://na7.salesforce.com/500A0000008UBgS project_key: JBEPP Creating custom implementations of the LocaleConfig and LocaleConfigService interfaces is not possible by extending the existing implementations. Most methods are declared final or private. The current implementations should be changed so that they can be easily extended. Otherwise unnecessary code duplication has to be done.
Link: Added: This issue Cloned from GTNPORTAL-2278
NEEDINFO: Added: Nobody
Link: Removed: This issue Cloned from GTNPORTAL-2278
Link: Added: This issue depends GTNPORTAL-2278
Help Desk Ticket Reference: Added: https://na7.salesforce.com/500A0000008UBgS
Release Notes Docs Status: Added: Not Yet Documented Release Notes Text: Added: CAUSE: CONSEQUENCE: FIX: RESULT:
Labels: Added: EPP_5_2_1_Candidate
Labels: Removed: EPP_5_2_1_Candidate
Release Notes Text: Removed: CAUSE: CONSEQUENCE: FIX: RESULT: Added: CAUSE: Many methods in LocaleConfigImpl, and LocaleConfigServiceImpl were final or private. CONSEQUENCE: Users were unable to reuse existing implementation by extending and overriding - they were forced to copy-paste in order to implement alternative behaviour. FIX: Remove final from methods, make private method protected. RESULT: Users should now be able to extend, and override the default LocaleConfig implementation.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: CAUSE: Many methods in LocaleConfigImpl, and LocaleConfigServiceImpl were final or private. CONSEQUENCE: Users were unable to reuse existing implementation by extending and overriding - they were forced to copy-paste in order to implement alternative behaviour. FIX: Remove final from methods, make private method protected. RESULT: Users should now be able to extend, and override the default LocaleConfig implementation.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,11 +1,2 @@ -CAUSE: Many methods in LocaleConfigImpl, and +It was discovered that many methods in LocaleConfigImpl, and -LocaleConfigServiceImpl were final or private. +LocaleConfigServiceImpl were declared final or private. Users were unable to reuse an existing implementation by extending and overriding the methods, and were forced to make a copy of the method to implement customized behavior. The fix removes the final declaration from these methods, and declares private methods as protected. This allows users to extend and override the default LocaleConfig implementation.- -CONSEQUENCE: Users were unable to reuse existing implementation by extending -and overriding - they were forced to copy-paste in order to implement -alternative behaviour. - -FIX: Remove final from methods, make private method protected. - -RESULT: Users should now be able to extend, and override the default -LocaleConfig implementation.