Looking over the EnterpriseLifeCycle class, I noticed that the el resolver is only added to the JSP ApplicationContext if a faces-config.xml is not found. I know that the webbeans-impl jar has an entry in the faces-config.xml that adds the el-resolver for JSF, but its seems like that shouldn't prevent JSPs in an application that uses some JSF pages from being able to reference a jcdi bean annotated with @Named.
Is this a question of performance? Does having the el-resolver registered with both JSF and JSP mean that we could end up executing the resolver twice if the bean isn't found? Somewhat related, I'm not sure looking for a faces-config.xml is the best way of checking to see if the application is using JSF. The JSF specification describes a web.xml context param (javax.faces.CONFIG_FILES) that can be used to define other configuration files. Sincerely, Joe
