Request for comments on Myfaces project statuses

[Mike Kienenberger]

I'm in the process of compiling the Myfaces board report for October.

Would anyone care to comment on the activity and health of the
following subprojects?  I've already written something up for
Trinidad, Tobago, and PortletBridge, which I've posted at the bottom,
but we can revise those if necessary.

JSF Implementation:
 - Apache Myfaces Core is ...

UI-Component Sets:
- Myfaces Tomahawk is ...

Add-ons and Extensions:

 - Apache MyFaces CODI is ...
 - Apache MyFaces Orchestra is ...
 - Apache MyFaces ExtVal is ...
 - Apache MyFaces Test is ...
 - Apache MyFaces Commons is ...
 - Apache MyFaces Ext-Scripting is ...
 - Apache MyFaces Sandbox is ...


UI-Component Sets:
 - Apache Tobago is healthy and active.

 - Apache Trinidad had three maintenance commits by two different new
contributors this quarter, which was encouraged by having issue
reporters submit fixes for their own issues.  There may still be life
in this project.

Add-ons and Extensions:
 - Apache MyFaces Portlet Bridge is dead.  Last developer commit was
Jan 2014.  We added a contributor who indicated interest in the
project in May, but no activity has been forthcoming.  We will
probably need assistance in moving this project to the attic.

[jira] [Commented] (MYFACES-3981) Unable to resolve Integer API as Lambda expression in a facelet

[Bill Lucy (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943975#comment-14943975
 ] 

Bill Lucy commented on MYFACES-3981:


You're right, this won't work with an pre-EL-3 implementation.  We will need to 
gate the fix with the EL version.  A more immediate problem is that this 
doesn't even compile with the current project setup - it looks like we compile 
against the EL 2.2 api/impl.

> Unable to resolve Integer API as Lambda expression in a facelet
> ---
>
> Key: MYFACES-3981
> URL: https://issues.apache.org/jira/browse/MYFACES-3981
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: JSR-344
>Affects Versions: 2.2.7
>Reporter: Anup
>Priority: Minor
> Attachments: myfaces-3981-2.2.8.patch
>
>
> Following testcases does not print anything in a facelet
> 
> 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (MYFACES-3981) Unable to resolve Integer API as Lambda expression in a facelet

[Bill Lucy (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943975#comment-14943975
 ] 

Bill Lucy edited comment on MYFACES-3981 at 10/5/15 8:36 PM:
-

You're right, this won't work with an pre-EL 3.0 implementation.  We will need 
to gate the fix with the EL version.  A more immediate problem is that this 
doesn't even compile with the current project setup - it looks like we compile 
against the EL 2.2 api/impl.


was (Author: wtlucy):
You're right, this won't work with an pre-EL-3.0 implementation.  We will need 
to gate the fix with the EL version.  A more immediate problem is that this 
doesn't even compile with the current project setup - it looks like we compile 
against the EL 2.2 api/impl.

> Unable to resolve Integer API as Lambda expression in a facelet
> ---
>
> Key: MYFACES-3981
> URL: https://issues.apache.org/jira/browse/MYFACES-3981
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: JSR-344
>Affects Versions: 2.2.7
>Reporter: Anup
>Priority: Minor
> Attachments: myfaces-3981-2.2.8.patch
>
>
> Following testcases does not print anything in a facelet
> 
> 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (MYFACES-3981) Unable to resolve Integer API as Lambda expression in a facelet

[Bill Lucy (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943975#comment-14943975
 ] 

Bill Lucy edited comment on MYFACES-3981 at 10/5/15 8:36 PM:
-

You're right, this won't work with an pre-EL-3.0 implementation.  We will need 
to gate the fix with the EL version.  A more immediate problem is that this 
doesn't even compile with the current project setup - it looks like we compile 
against the EL 2.2 api/impl.


was (Author: wtlucy):
You're right, this won't work with an pre-EL-3 implementation.  We will need to 
gate the fix with the EL version.  A more immediate problem is that this 
doesn't even compile with the current project setup - it looks like we compile 
against the EL 2.2 api/impl.

> Unable to resolve Integer API as Lambda expression in a facelet
> ---
>
> Key: MYFACES-3981
> URL: https://issues.apache.org/jira/browse/MYFACES-3981
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: JSR-344
>Affects Versions: 2.2.7
>Reporter: Anup
>Priority: Minor
> Attachments: myfaces-3981-2.2.8.patch
>
>
> Following testcases does not print anything in a facelet
> 
> 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MYFACES-3981) Unable to resolve Integer API as Lambda expression in a facelet

[Thomas Andraschko (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943985#comment-14943985
 ] 

Thomas Andraschko commented on MYFACES-3981:


Yep thats true - same as: https://issues.apache.org/jira/browse/MYFACES-4008

We could of course use reflection but thats not a good way IMO.
We should update the servlet 3.1 (for ticket 4008) and EL 3 and do something 
like:
if (el3Available) {ImportHandler}

This should also work fine for el 2.2 as the code is only executed with EL 3.0.
We use some of such statements in PrimeFaces and this is working fine.

[~lu4242] WDYT?

> Unable to resolve Integer API as Lambda expression in a facelet
> ---
>
> Key: MYFACES-3981
> URL: https://issues.apache.org/jira/browse/MYFACES-3981
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: JSR-344
>Affects Versions: 2.2.7
>Reporter: Anup
>Priority: Minor
> Attachments: myfaces-3981-2.2.8.patch
>
>
> Following testcases does not print anything in a facelet
> 
> 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Request for comments on Myfaces project statuses

[Leonardo Uribe]

Hi

These are my personal comments:

2015-10-05 13:05 GMT-05:00 Mike Kienenberger :

> I'm in the process of compiling the Myfaces board report for October.
>
> Would anyone care to comment on the activity and health of the
> following subprojects?  I've already written something up for
> Trinidad, Tobago, and PortletBridge, which I've posted at the bottom,
> but we can revise those if necessary.
>
> JSF Implementation:
>  - Apache Myfaces Core is ...
>
>
I think the project is healthy, but we are on a maintenance stage, which
means the activity is reduced, because there are less and less issues
to be solved. A release could be done soon.


> UI-Component Sets:
> - Myfaces Tomahawk is ...
>
>
No activity on this part. The reason is over the time, many features and
ideas of  Tomahawk were included into jsf spec, which at the end looks
better, but reduce the need of the specific hacks that Tomahawk provides,
even more with jsf 2.2 html5, composite components and, passthrough
attributes. There are some components that are still useful.

Add-ons and Extensions:
>
>  - Apache MyFaces CODI is ...
>

As we all know Apache MyFaces CODI is on maintenance stage too,
because it was replaced by DeltaSpike, so the new development is
happening there, which at the end looks better.


>  - Apache MyFaces Orchestra is ...
>

Few activity because for new projects it is better to use CDI and
DeltaSpike.


>  - Apache MyFaces Test is ...
>

There is activity on this part, because it is a fundamental component for
MyFaces Core.


>  - Apache MyFaces Commons is ...
>

This project just provide some small utilities.


>  - Apache MyFaces Sandbox is ...
>
>

No activity on this part, because it takes a lot of effort to build
another component library, given the good quality options
provided by other jsf libraries. In practice JSF components that
relies on some kind of javascript are not 100% reliable across
different JSF component libraries, which makes really hard to
build components, usually because javascript libraries conflict
between each other and because there is not an standard
javascript loader for JSF.

regards,

Leonardo Uribe


>
> UI-Component Sets:
>  - Apache Tobago is healthy and active.
>
>  - Apache Trinidad had three maintenance commits by two different new
> contributors this quarter, which was encouraged by having issue
> reporters submit fixes for their own issues.  There may still be life
> in this project.
>
> Add-ons and Extensions:
>  - Apache MyFaces Portlet Bridge is dead.  Last developer commit was
> Jan 2014.  We added a contributor who indicated interest in the
> project in May, but no activity has been forthcoming.  We will
> probably need assistance in moving this project to the attic.
>

[jira] [Commented] (MYFACES-3981) Unable to resolve Integer API as Lambda expression in a facelet

[Leonardo Uribe (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944429#comment-14944429
 ] 

Leonardo Uribe commented on MYFACES-3981:
-

We cannot really change the dependencies of core. Instead, the used hack is do 
a check on the classpath to identify when EL 3.0 is being used.

Take a look at org.apache.myfaces.el.unified.ResolverBuilderForFaces

For implement JSF 2.2 section 5.6.2.8 (EL 3.0 support), there are some lines 
that check for "javax.el.StaticFieldELResolver" class.

This is not a bug, instead it is an improvement (it should be enabled/disabled 
using a web config param, by default disabled), because JSF 2.2 is java 6 
compatible, not java 8. The right way to do it is add a EL Resolver at the end 
of the chain (after list.add(new BeanELResolver()) or maybe use an alternate 
ScopedAttributeResolver) and on that resolver add the missing lines (the ones 
provided in the patch), just like javax.el.StaticFieldELResolver is added.

> Unable to resolve Integer API as Lambda expression in a facelet
> ---
>
> Key: MYFACES-3981
> URL: https://issues.apache.org/jira/browse/MYFACES-3981
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: JSR-344
>Affects Versions: 2.2.7
>Reporter: Anup
>Priority: Minor
> Attachments: myfaces-3981-2.2.8.patch
>
>
> Following testcases does not print anything in a facelet
> 
> 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)