From: Neil Griffin <neil.griffin_at_portletfaces.org>
Date: Wed, 7 Dec 2016 18:45:26 -0500

Hi Manfred,

Because of the "first half of next year" timeline for completing JSF 2.3, the Liferay Faces team has escalated the priority of compatibility testing and repairs.

Although Liferay hasn't yet filed a JSR for Portlet 3.0 + JSF 2.3, the master branches of the bridge are setup for that configuration:
- https://github.com/liferay/liferay-faces-bridge-api
- https://github.com/liferay/liferay-faces-bridge-impl

1) What the Liferay Faces team has done:

- https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-790
        - Lots of coordination with a very patient Bauke Scholtz to get rid of hacks in the bridge by fortifying the capabilities of jsf.js and the ParitalViewContext
        - The Spec document and/or JavaDoc may require final edits regarding the RENDER_ALL_MARKER -- I'll have to check with Bauke

- Initial testing of Mojarra 2.3 in Pluto 3.0 with <faces-config version="2.2"> (compatibility mode)

2) The Liferay Faces team is currently working on:

- https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1433
        - Testing the proposed fix in Pluto 3.0

- https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-790
        - As a final task, getting the render="@all" use case to work in both webapps and portlets
        - The Spec document may require final edits -- I'll have to check with Bauke

- https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1421
        - Working with Bauke to clarify Spec language and JavaScript docs

- https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1423
        - Validating the design for the portlet use case and testing in Pluto 3.0

- Testing <faces-config version="2.3"> opt-in, but running into a problem in which dynamic CDI producers like the ResourceHandlerProducer are creating @RequestScoped instances. The context for @PortletRequestScope should be handling that but it's not working right now.

3) What the Liferay Faces team is not going to do:

- Not going to define requirements in the bridge for <f:websocket/> because WebSocket was considered to be out-of-scope for Portlet 3.0
- Instead, we will be studying the possibility of vendor-specific support

Thanks,

Neil

> On Dec 7, 2016, at 9:59 AM, manfred riem <manfred.riem_at_oracle.com> wrote:
>
> Hi Neil,
>
> Can you please tell me what you
>
> 1) have done
> 2) are currently doing (and which can be completed and which is not)
> 3) are not going to do
>
> And for 1) and 2) if there is going to be a need for any text in the
> Specification (the PDF document).
>
> Kind regards,
> Manfred Riem