You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2014/09/23 23:22:34 UTC
[jira] [Commented] (MYFACES-3927) Myfaces 2.2.4 not compatible with
Google App Engine
[ https://issues.apache.org/jira/browse/MYFACES-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145465#comment-14145465 ]
Leonardo Uribe commented on MYFACES-3927:
-----------------------------------------
It looks we have one more reason to make it work for Servlet 2.5. It looks like GAE has a ticket open since 2010:
https://code.google.com/p/googleappengine/issues/detail?id=3091
And we are in 2014 and nothing has changed. I tried to run 2.2.5 with Tomcat 6.0.41 and it works until the call to cookie.setHttpOnly(true) occur. Obviously, h:inputFile relies on servlet 3.0 so it will not work either, but besides that it could be an incentive to make it work, because there are some good features in JSF 2.2 like resource library contracts, HTML5 friendly markup, Faces Flows and so on that are worth.
> Myfaces 2.2.4 not compatible with Google App Engine
> ---------------------------------------------------
>
> Key: MYFACES-3927
> URL: https://issues.apache.org/jira/browse/MYFACES-3927
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.2.4
> Environment: Google App Engine for Java
> Reporter: Paul Jenq
>
> Google App Engine (GAE) for Java uses Servlet 2.5 (Jetty). Myfaces 2.2.4 starts to use Servlet 3.0 calls for http cookies, as described in the issue MYFACES-3923. It is incompatible with GAE (until GAE updated to servlet 3.0 that, for some reasons, is not happening). Can the issue be solved by introducing a context parameter to configure Myfaces 2.2.* to use servlet 2.5 or servlet 3.0?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [jira] [Commented] (MYFACES-3927) Myfaces 2.2.4 not compatible
with Google App Engine
Posted by Mike Kienenberger <mk...@gmail.com>.
On Tue, Sep 23, 2014 at 5:22 PM, Leonardo Uribe (JIRA) wrote:
> It looks we have one more reason to make it work for Servlet 2.5. It looks like GAE has a ticket open since 2010:
>
> https://code.google.com/p/googleappengine/issues/detail?id=3091
>
> And we are in 2014 and nothing has changed. I tried to run 2.2.5 with
> Tomcat 6.0.41 and it works until the call to cookie.setHttpOnly(true) occur.
> Obviously, h:inputFile relies on servlet 3.0 so it will not work either, but
> besides that it could be an incentive to make it work, because there are
> some good features in JSF 2.2 like resource library contracts, HTML5
> friendly markup, Faces Flows and so on that are worth.
+0. Doesn't matter to me. While there's no reason to intentionally
break backward compatibility, there's also no reason to let
non-adoption of Servlet 3.0 interfere with JSF 2.2 development.
The platforms my client uses only supported Servlet 2.5 until last
month, so we've stuck with MyFaces 2.1 for that reason, but I don't
expect MyFaces 2.2 development to stop just because I can't upgrade my
projects.