[
https://issues.apache.org/jira/browse/WICKET-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Teppo Kurki updated WICKET-1763:
--------------------------------
Priority: Minor (was: Major)
Description:
Finding the guice annotations via reflection for each Component instantiation
is a rather heavyweight operation.
This causes considerable overhead with large lists that have complicated
component structure per row, which is totally unnecessary for stock wicket
components that do not contain any Guice annotations.
was:Finding the guice annotations for each object instantiation is a rather
heavyweight operation. This causes considerable overhead with large lists that
have complicated component structure per row, which is totally unnecessary for
stock wicket components that do not contain any Guice annotations.
Summary: GuiceComponentInjector overhead for non-injectable Components
(was: Cache the injection flag per class to improve performance)
> GuiceComponentInjector overhead for non-injectable Components
> -------------------------------------------------------------
>
> Key: WICKET-1763
> URL: https://issues.apache.org/jira/browse/WICKET-1763
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-guice
> Affects Versions: 1.3.3, 1.3.4
> Reporter: Teppo Kurki
> Priority: Minor
> Attachments: InjectionFlagCachingGuiceComponentInjector.java
>
>
> Finding the guice annotations via reflection for each Component instantiation
> is a rather heavyweight operation.
> This causes considerable overhead with large lists that have complicated
> component structure per row, which is totally unnecessary for stock wicket
> components that do not contain any Guice annotations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
