[
https://issues.apache.org/jira/browse/FELIX-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804083#action_12804083
]
Felix Meschberger edited comment on FELIX-1051 at 1/23/10 2:08 PM:
-------------------------------------------------------------------
I have applied a variation of the patch in Rev. 902097
All requests handled by web console plugins are now wrapped by response
wrapper, which installs a Writer filter if the response is a text/html
response. This writer filter recognizes variables of the pattern ${name} and
tries to replace that part of the output with another string:
* If a variable of that name exists, the value of that variable is used.
* Otherwise if a resource bundle provides a translated string for the name,
that string is used.
* Otherwise the name itself is just placed in the output
The resource bundle is created using bundle localization of the
plugin-providing bundle and bundle localization of the Web Console bundle
itself. To get at the localisation resources, the Bundle-Localization bundle
header is used according to Section 3.10 Localization in the Core
Specification. Any localization in the providing bundle takes preference on any
localization in the web console bundle.
The variable resolution is provided by the plugin at request time. Currently
the plugin is checked whether it implements the new VariabledResolver interface
and if so, the plugin is directly called to resovle variables. This works fine
for "static" variables, but fails completely for request-time variables like
for example a bundle list to be expanded for the current request. Some more
thinking has to go in there to be able to make this request-dependent.....
was (Author: fmeschbe):
I have applied a variation of the patch in Rev.
All requests handled by web console plugins are now wrapped by response
wrapper, which installs a Writer filter if the response is a text/html
response. This writer filter recognizes variables of the pattern ${name} and
tries to replace that part of the output with another string:
* If a variable of that name exists, the value of that variable is used.
* Otherwise if a resource bundle provides a translated string for the name,
that string is used.
* Otherwise the name itself is just placed in the output
The resource bundle is created using bundle localization of the
plugin-providing bundle and bundle localization of the Web Console bundle
itself. To get at the localisation resources, the Bundle-Localization bundle
header is used according to Section 3.10 Localization in the Core
Specification. Any localization in the providing bundle takes preference on any
localization in the web console bundle.
The variable resolution is provided by the plugin at request time. Currently
the plugin is checked whether it implements the new VariabledResolver interface
and if so, the plugin is directly called to resovle variables. This works fine
for "static" variables, but fails completely for request-time variables like
for example a bundle list to be expanded for the current request. Some more
thinking has to go in there to be able to make this request-dependent.....
> Localize the web console
> ------------------------
>
> Key: FELIX-1051
> URL: https://issues.apache.org/jira/browse/FELIX-1051
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
> Affects Versions: webconsole-1.2.8
> Reporter: Carsten Ziegeler
> Assignee: Felix Meschberger
> Attachments: FELIX-1051.patch
>
>
> We should think about localizing the web console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
