struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukasz Lenart (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (WW-4762) DefaultLocalizedTextProvider refactoring
Date Fri, 17 Mar 2017 11:10:41 GMT

     [ https://issues.apache.org/jira/browse/WW-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lukasz Lenart updated WW-4762:
------------------------------
    Description: 
Now that DefaultLocalizedTextProvider is a bean, would it be possible to refactor the code
to allow an override so we can change the default behavior on the package searching for the
resource.properties files.  Currently is does an extensive search up the class interfaces
first which on busy screens slows things down and is an unnecessary overhead. 

ie As I have migrated from struts1 my main UI resources are in the default ApplicationResources.properties
file and are shared across struts ui classes in various packages. I would not want to duplicate
the .properties entries for maintenance etc.
I would then want to search the default ApplicationResources.properties first and then package
class (for validation messages) and then possibly up the interfaces (which would not make
sense for me as I do not use this logic).

Discussion related to this
http://markmail.org/message/v2oc6c35swfwzwid

  was:
Now that DefaultLocalizedTextProvider is a bean, would it be possible to refactor the code
to allow an override so we can change the default behavior on the package searching for the
resource.properties files.  Currently is does an extensive search up the class interfaces
first which on busy screens slows things down and is an unnecessary overhead. 

ie As I have migrated from struts1 my main UI resources are in the default ApplicationResources.properties
file and are shared across struts ui classes in various packages. I would not want to duplicate
the .properties entries for maintenance etc.
I would then want to search the default ApplicationResources.properties first and then package
class (for validation messages) and then possibly up the interfaces (which would not make
sense for me as I do not use this logic).



> DefaultLocalizedTextProvider refactoring
> ----------------------------------------
>
>                 Key: WW-4762
>                 URL: https://issues.apache.org/jira/browse/WW-4762
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Greg Huber
>            Priority: Minor
>             Fix For: 2.5.next
>
>
> Now that DefaultLocalizedTextProvider is a bean, would it be possible to refactor the
code to allow an override so we can change the default behavior on the package searching for
the resource.properties files.  Currently is does an extensive search up the class interfaces
first which on busy screens slows things down and is an unnecessary overhead. 
> ie As I have migrated from struts1 my main UI resources are in the default ApplicationResources.properties
file and are shared across struts ui classes in various packages. I would not want to duplicate
the .properties entries for maintenance etc.
> I would then want to search the default ApplicationResources.properties first and then
package class (for validation messages) and then possibly up the interfaces (which would not
make sense for me as I do not use this logic).
> Discussion related to this
> http://markmail.org/message/v2oc6c35swfwzwid



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message