[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1978) Minimize the performance cost of calling getter in JBoss EL

Julien Kronegg (JIRA) jira-events at lists.jboss.org
Wed Feb 11 18:58:44 EST 2009

    [ https://jira.jboss.org/jira/browse/JBSEAM-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12452282#action_12452282 ] 

Julien Kronegg commented on JBSEAM-1978:

I've made a few experiments on Interceptor-based method result caching http://www.seamframework.org/Community/HowtoAvoidMethodOrGetterToBeCalledSeveralTimesByCachingResult
Basically, we are cutting the number of Interceptors from 5 to 2. Altough I did not make any measurement, the stack trace are shorter.
It works well for non-lazy initialized data, but I still have LazyInitializationException because the Session which created the lazy-initialized entity is no more active.
Anyway, this could be a search path...

> Minimize the performance cost of calling getter in JBoss EL
> -----------------------------------------------------------
>                 Key: JBSEAM-1978
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-1978
>             Project: Seam
>          Issue Type: Feature Request
>          Components: EL, Performance and Scalability
>            Reporter: Mikhail Grushinskiy
>            Assignee: Jay Balunas
>             Fix For: 2.1.2.CR1
> Minimize the performance cost of calling getter in JBoss EL
> bean.property is the most common EL construct used in all JSF applications.
> The cost of calling property getter in EL is more important to overall JSF application performance (specifically rendering phase)
> See also
> http://jira.jboss.com/jira/browse/JBSEAM-1977

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


More information about the seam-issues mailing list