You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Ari hadi (JIRA)" <de...@myfaces.apache.org> on 2008/08/25 21:39:44 UTC
[jira] Created: (TRINIDAD-1191) Delayed loading of renderers to
facilitate faster start up time
Delayed loading of renderers to facilitate faster start up time
----------------------------------------------------------------
Key: TRINIDAD-1191
URL: https://issues.apache.org/jira/browse/TRINIDAD-1191
Project: MyFaces Trinidad
Issue Type: Improvement
Reporter: Ari hadi
Class loading optimization to lazily loads renderers, since 20% of the time used for opening the file the first time is for class loading.
Right now the Trinidad RenderKitBase class has support for loading renderer mappings from a RenderKit-specific config file.
In the case of the rich client render kit, the file is located at "META-INF/oracle.adf.rich.renderkit". We should be able to tweak this code to grab all files found at the specific path instead of just one. This will allow any other custom component developers to lazily load their Renderers by providing their own mapping file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1191) Delayed loading of renderers to
facilitate faster start up time
Posted by "Ari hadi (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ari hadi updated TRINIDAD-1191:
-------------------------------
Status: Patch Available (was: Open)
> Delayed loading of renderers to facilitate faster start up time
> ----------------------------------------------------------------
>
> Key: TRINIDAD-1191
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1191
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Reporter: Ari hadi
> Attachments: RenderKitBase.java
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Trinidad's RenderKitBase class has support for optimized loading of renderer. Class loading optimization will lazily loads renderers and reduces the loading time, since 20% of the time used for opening the file the first time is for class loading.
> Renderers that are provided in the RenderKit-specific config file will be loaded lazily. This mapping file is similar to the one in "META-INF/oracle.adf.rich.renderkit".
> Right now, it will only look for one copy of the renderkit-specific config file. We should be able to tweak this code to grab all files found at the specific path instead of just one. This will allow any other custom component developers to lazily load their Renderers by providing their own mapping file.
> Note: At the moment, we are doing more tests to verify the lazy renderer to load other custom components lazily. Please do not commit this patch until then.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1191) Delayed loading of renderers to
facilitate faster start up time
Posted by "Ari hadi (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ari hadi updated TRINIDAD-1191:
-------------------------------
Status: Open (was: Patch Available)
> Delayed loading of renderers to facilitate faster start up time
> ----------------------------------------------------------------
>
> Key: TRINIDAD-1191
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1191
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Reporter: Ari hadi
> Attachments: RenderKitBase.java
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Trinidad's RenderKitBase class has support for optimized loading of renderer. Class loading optimization will lazily loads renderers and reduces the loading time, since 20% of the time used for opening the file the first time is for class loading.
> Renderers that are provided in the RenderKit-specific config file will be loaded lazily. This mapping file is similar to the one in "META-INF/oracle.adf.rich.renderkit".
> Right now, it will only look for one copy of the renderkit-specific config file. We should be able to tweak this code to grab all files found at the specific path instead of just one. This will allow any other custom component developers to lazily load their Renderers by providing their own mapping file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1191) Delayed loading of renderers to
facilitate faster start up time
Posted by "Ari hadi (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ari hadi updated TRINIDAD-1191:
-------------------------------
Status: Patch Available (was: Open)
> Delayed loading of renderers to facilitate faster start up time
> ----------------------------------------------------------------
>
> Key: TRINIDAD-1191
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1191
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Reporter: Ari hadi
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Trinidad's RenderKitBase class has support for optimized loading of renderer. Class loading optimization will lazily loads renderers and reduces the loading time, since 20% of the time used for opening the file the first time is for class loading.
> Renderers that are provided in the RenderKit-specific config file will be loaded lazily. This mapping file is similar to the one in "META-INF/oracle.adf.rich.renderkit".
> Right now, it will only look for one copy of the renderkit-specific config file. We should be able to tweak this code to grab all files found at the specific path instead of just one. This will allow any other custom component developers to lazily load their Renderers by providing their own mapping file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1191) Delayed loading of renderers to
facilitate faster start up time
Posted by "Matthias Weßendorf (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Weßendorf updated TRINIDAD-1191:
-----------------------------------------
Resolution: Fixed
Fix Version/s: 1.0.10-core
1.2.10-core
Assignee: Matthias Weßendorf
Status: Resolved (was: Patch Available)
> Delayed loading of renderers to facilitate faster start up time
> ----------------------------------------------------------------
>
> Key: TRINIDAD-1191
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1191
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Reporter: Ari hadi
> Assignee: Matthias Weßendorf
> Fix For: 1.2.10-core, 1.0.10-core
>
> Attachments: 1191-patch.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Trinidad's RenderKitBase class has support for optimized loading of renderer. Class loading optimization will lazily loads renderers and reduces the loading time when the RenderKit is initialized. This is particularly important when the RenderKit is initialized when starting a J2EE container to debug a JSF application in a development environment. In our experience, lazily loading renderers during the start of a debug/run cycle can cut the startup time by 20%.
> Renderers that are listed in the RenderKit-specific config file will be loaded lazily, e.g. META-INF/rich.renderkit. The renderers in It should have the format
> "[component family]|[renderer type]=[Renderer class]"
> Right now, RenderKitBase will only look for one copy of the renderkit-specific config file. We should be able to tweak this code to grab all files found at the path instead of just one (provided in the patch). This will allow any other custom component developers to lazily load their Renderers by providing their own mapping file.
> We have done more tests to verify the lazy renderer works to load other custom components.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.