[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2141) Support for EL without reflection for better JSF performance
[ http://jira.jboss.com/jira/browse/JBSEAM-2141?page=comments#action_12383976 ]
Mikhail Grushinskiy commented on JBSEAM-2141:
---------------------------------------------
Not sure I understand your point about looking up EL name.
When you parse (initialize xhtml page) you generate and store a reference to bytecode
entry for each EL expression
and call it passing appropriate beans used in this EL expression when you need to evaluate
that expression.
In current implementation for
#{myBean.subBean.property}
you have to lookup getter for subBean property, invoke it and then resolve to getter for
'property' and invoke it.
While whole thing could have been precompiled into byte-code and take myBean as a
parameter
Support for EL without reflection for better JSF performance
------------------------------------------------------------
Key: JBSEAM-2141
URL: http://jira.jboss.com/jira/browse/JBSEAM-2141
Project: JBoss Seam
Issue Type: Feature Request
Components: EL
Reporter: Mikhail Grushinskiy
Support for EL without reflection for better JSF performance.
The idea is to add a new tag to declare types of the variables used on a page and use
this type information
to compile EL expressions into byte-code during initialization (deployment)
Ex:
If the page contains at the beginning
<s:typedef var="myBean" class="com.company.package.Bean" />
then all EL expressions can be compiled into bytecode at initialization time (and no
reflection will be used for myBean access.
<h:outputText value="#{myBean.subBean.property}"
rendered="#{myBean.renderText}" />
Some examples of implementation of compiled EL can be found here
http://sixlegs.com/blog/java/compiled-el.html
This should help much with JSF performance issues
Thanks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira