Hello All,
I like the new approach. This will allow users of the technology to keep up
todate using a number of the new features without having to worry about a
hard-fast requirement for CDI.
It also allows users the opportunity to move forward with CDI, or migrate
existing applications to CDI when appropriate.
The changes using faces-config.xml are minimal.
Do we want to have some functionality to allow it to be set
programmatically? I have had some cases where I want to load a servlet,
filter, etc. programmatically. I have found cases where there is some
expectation of a file like web.xml existing, but since the servlet was
loaded programmatically, certain configurations could not be set.
John
____________________________
John Yeary
____________________________
*NetBeans Dream Team*
*President Greenville Java Users GroupJava Users Groups Community
LeaderJava Enterprise Community Leader*
____________________________
<
http://javaevangelist.blogspot.com/> <
https://twitter.com/jyeary>
<
http://www.youtube.com/johnyeary> <
http://www.linkedin.com/in/jyeary>
<
https://plus.google.com/112146428878473069965>
<
http://www.facebook.com/jyeary>
<
http://feeds.feedburner.com/JavaEvangelistJohnYearysBlog>
<
http://netbeans.org/people/84414-jyeary>
"Far better it is to dare mighty things, to win glorious triumphs, even
though checkered by failure, than to take rank with those poor spirits who
neither enjoy much nor suffer much, because they live in the gray twilight
that knows not victory nor defeat."
-- Theodore Roosevelt
On Wed, Oct 8, 2014 at 5:18 PM, manfred riem <manfred.riem_at_oracle.com>
wrote:
> Hi all,
>
> After working on https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-
> 1311 it has become clear to Ed and I that there is more work to be done
> so I have temporarily reverted the work done for 1311 and I will now
> describe what we think would be a good way forward.
>
> Use case #1 - Old applications prior to Servlet 4.0 / JSF 2.3
>
> Make sure this keeps working as usual without making it hard CDI
> dependent. Which means we are not going to change in the EL resolvers, the
> EL resolver chain or how the integration is currently done. This will
> maintain our backwards compatibility.
>
> Use case #2 - New application wanting to use Servlet 4.0 / JSF 2.3
>
> 1. Required to either have a web.xml with version 4.0 or a
> WEB-INF/faces-config.xml stating version 2.3, as this will activate the new
> behavior.
>
> 2. Let CDI do most of the EL resolving, which means adding producers for
> the old EL resolvers (e.g. ImplicitObject, Composite etc).
>
> 3. Rework the EL resolver chain to use the new CDI EL Resolver plus any
> other EL resolvers that we need.
>
> 4. Define the default producers in a javax.faces package so they are
> consistent between JSF implementations and allow for overriding.
>
> 5. By making it an opt-in the component vendor / developer will have to
> support the new requirements if they want to take advantage of these new
> capabilities.
>
> Comments, thoughts?
>
> Regards,
> Manfred
>
>