[
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)
