You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Bernd Bohmann (JIRA)" <de...@myfaces.apache.org> on 2017/04/25 12:50:04 UTC
[jira] [Resolved] (TRINIDAD-2539) Make Trinidad 2.1 compatible with
JSF 2.2
[ https://issues.apache.org/jira/browse/TRINIDAD-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bernd Bohmann resolved TRINIDAD-2539.
-------------------------------------
Resolution: Fixed
Partially resolved.
Please reopen if you find a new issue related jsf 2.2
> Make Trinidad 2.1 compatible with JSF 2.2
> -----------------------------------------
>
> Key: TRINIDAD-2539
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2539
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Affects Versions: 2.1.1-core
> Reporter: Leonardo Uribe
> Assignee: Bernd Bohmann
> Fix For: 2.1.3-core
>
>
> After 2.1.1 release, and according to some reports, I notice trinidad 2.1.x is compatible with JSF 2.1 but there are some issues with JSF 2.2:
> - file upload,
> - deploy multiple copies of trinidad on the same container.
> ...
> I think these issues deserve some attention. The problem is historically trinidad is a frameworks that overrides some existing JSF stuff and make it on its own way. Most of the changes between JSF 2.1 and JSF 2.2 are incremental, so I don't see why trinidad could work well in JSF 2.2. Let's see what happen.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)