Hi,
On Mon, Aug 24, 2015 at 1:57 PM, Edward Burns <edward.burns_at_oracle.com> wrote:
>>>>>> On Fri, 21 Aug 2015 21:45:08 +0000, arjan_t_at_java.net said:
> I realize this is temporary, but does this impact existing JSF 2.2 apps
> or is the "flowScopex" implicit object only relevant of you opt-in to
> the new producers?
"flowScopex" is indeed temporary, only intended to be there while we
flesh out the code. The commit was only done in the 2.3 trunk, so it
doesn't affect existing 2.2 apps that use a Mojarra 2.2 library.
> Also, can you or Manfred please explain to the list how the developer
> does opt-in to the new producers?
We tried a couple of approaches. Initially it was the 2.3 faces-config
deployment descriptor, but this was changed a while ago to a context
parameter in web.xml.
Currently the following that enables it:
<context-param>
<param-name>javax.faces.ENABLE_CDI_RESOLVER_CHAIN</param-name>
<param-value>true</param-value>
</context-param>
The default is, as one may expect here, "false".
Now this method is not entirely ideal. The problem is that web.xml can
not be read in a fully portable way from an extension. It's only
really available to external code when the ServletContext is
available. A very early moment is the ServletContainerInitializer, but
this one too is too late for CDI extensions, which generally execute
before that.
There are a variety of alternative options that we're currently looking at.
Kind regards,
Arjan Tijms
>
> Thanks,
>
> Ed
>
> --
> | edward.burns_at_oracle.com | office: +1 407 458 0017
> | 51 Business days til JavaOne 2015
> | 66 Business days til DOAG 2015