Actually not directly related but to a sidenote, I personally think we
lose significant startup performance the way we parse the xml files via
commons-digester, StAX would be a way faster alternative (although it
probably would introduce about twice as much code because the digester
api relies on reflection)
Am 24.09.10 14:33, schrieb Martin Koci:
Hi,
since JSF 2.0 JSP support and<managed-bean> are deprecated. Since 1.2
same for javax.faces.el.
For performace reasons I suggest find a way how disable following:
1) Managed Bean support (o.a.m.SUPPORT_MANAGED_BEANS=false)
if this flag is false, myfaces will not install ManagedBeanResolver and
will skip managed beans processing during startup (or outputs a warning
if managed bean is found and this flag is false).
2) VariableResolver and PropertyResolver
(o.a.m.SUPPORT_JAVAX_FACES_EL=false)
myfaces will not install VariableResolverImpl and
VariableResolverToELResolver and PropertyResolver implementations
3) (o.a.m.SUPPORT_JSP=false)
if this flag is false myfaces will not install FacesCompositeELResolver
and will skip JSP initializer during startup. FacesCompositeELResolver
is related to VariableResolverImpl, maybe this can be one paramater.
Those are only suggestions. I did some initial profiling and when "old"
technogies are disabled myfaces gain significant performance boost,
especially in render response phase.
Another solution for ELResolvers only is use of comparator but this does
not allow skip certain parts of code.
WDYT?
Kočičák
