You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Valentin Valchev (JIRA)" <ji...@apache.org> on 2012/08/15 16:24:37 UTC
[jira] [Commented] (FELIX-2266) Dynamically get
ConfigurationPrinter services on demand
[ https://issues.apache.org/jira/browse/FELIX-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435146#comment-13435146 ]
Valentin Valchev commented on FELIX-2266:
-----------------------------------------
Hmm, I was looking at the code and it seems, that this could be unnecessary. The reason we wanted that feature, was to reduce the initial startup time and make sure that the printers are not instantiated when the plugin is not opened.
At the moment, the printers services are retrieved not immediately, but on the first attempt to render the Configuration Status plugin. It is true, that now all printers are initialized on that first rendering, but for me, that is acceptable. I don't think, that it's worth to optimize the current behavior even more.
So I vote for canceling the request.
> Dynamically get ConfigurationPrinter services on demand
> -------------------------------------------------------
>
> Key: FELIX-2266
> URL: https://issues.apache.org/jira/browse/FELIX-2266
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
> Affects Versions: webconsole-3.0.0
> Reporter: Felix Meschberger
>
> Much like FELIX-2246 does for Web Console Plugins the ConfigurationRender class should dynamically access ConfigurationPrinter services on-demand.
> This requires two things:
> * ConfigurationPrinter should register with their title (along with the label) as a service property
> * The internal ConfigurationPrinter proxy must be extended to cope for lazy service access
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira