You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@myfaces.apache.org by "Thomas Andraschko (JIRA)" <de...@myfaces.apache.org> on 2017/08/27 20:23:00 UTC

[jira] [Resolved] (MYFACES-2582) Publish useful container capability flags into ServletContext

     [ https://issues.apache.org/jira/browse/MYFACES-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Andraschko resolved MYFACES-2582.
----------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.3.0

As the 3 versions are not synchronized currently, i just did a cleanup on these classes.
I think it's ok to leave it for now.

> Publish useful container capability flags into ServletContext
> -------------------------------------------------------------
>
>                 Key: MYFACES-2582
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2582
>             Project: MyFaces Core
>          Issue Type: Improvement
>          Components: JSR-314
>    Affects Versions: 2.0.0-beta-2
>            Reporter: Jan-Kees van Andel
>            Assignee: Jan-Kees van Andel
>            Priority: Minor
>             Fix For: 2.3.0
>
>
> Currently, we have 3 identical "ExternalSpecifications" classes, in 3 separate packages.
> They are getting more complex and the duplication becomes cumbersome.
> A solution might be to enhance the StartupServletContextListener class to let it publish those container flags into the ServletContext, so the other classes can easily reuse them.
> See Jakob's comment on MYFACES-2565



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)