[
https://jira.jboss.org/jira/browse/JBSEAM-4268?page=com.atlassian.jira.pl...
]
Riccardo Serafin updated JBSEAM-4268:
-------------------------------------
Attachment: Component.java
Init.java
SeamELResolver.java
Attaching the relevant method from a test implementation I did on 2.2.0. If interested, I
can provide a proper patch for the last code version. However, it would need careful
review 'cos for sure I'm missing something...
Speed up SeamELResolver by avoiding a full scan of all imported
namespaces
--------------------------------------------------------------------------
Key: JBSEAM-4268
URL:
https://jira.jboss.org/jira/browse/JBSEAM-4268
Project: Seam
Issue Type: Feature Request
Affects Versions: 2.2.0.CR1
Reporter: Riccardo Serafin
Attachments: Component.java, Init.java, SeamELResolver.java
See post in the seam forum
(
http://www.seamframework.org/Community/212PerformanceRegressionInMessages) and
JBSEAM-4244.
Basically, I'd suggest two things in order to speed up the resolveBase method of
SeamELResolver:
1) Avoid going through all imported namespaces when looking up a property by caching
known component and factory names in imported namespaces at init time.
2) Allow resolution of components used very often, like messages, before looking in all
the stateful scopes, for sure at least before going through all imported name spaces.
Moreover, it would be nice to have some way to extend/bypass/configure the SeamELResolver
to allow application dependent optimization.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira