[
https://issues.apache.org/jira/browse/MYFACES-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038692#comment-13038692
]
Martin Kočí commented on MYFACES-3078:
--------------------------------------
Sorry about that, patch was really buggy.
>From my original mail: "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 parameter."
I don't understand the code about VariableResolverImpl and
FacesCompositeELResolver fully - it seems FacesCompositeELResolver creates a
entry in facesContext.attributes and VariableResolverImpl is the only one who
reads it.
Create general oam.SUPPORT_JSP_AND_FACES_EL parameter and disable both if
false? I think nobody uses old javax.faces.el with JSF 2.0 implementation
> performance: allow to disable JSP support
> -----------------------------------------
>
> Key: MYFACES-3078
> URL: https://issues.apache.org/jira/browse/MYFACES-3078
> Project: MyFaces Core
> Issue Type: New Feature
> Components: General
> Affects Versions: 2.0.5-SNAPSHOT, 2.1.0-SNAPSHOT
> Reporter: Martin Kočí
> Assignee: Martin Kočí
> Priority: Minor
> Attachments: MYFACES-3078-core-2.patch, MYFACES-3078-shared-2.patch,
> MYFACES-3078.patch
>
>
> Since JSF 2.0 JSP are deprecated. Allow:
> o.a.m.SUPPORT_JSP=false|true
> if this flag is false myfaces will not install FacesCompositeELResolver
> and will skip JSP initializer during startup
> see full discussion here:
> http://www.mail-archive.com/[email protected]/msg49177.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
