[jira] Updated: (ADFFACES-108) Attribute map, scope maps and JSF 1.2

["Matthias Weßendorf (JIRA)" <ad...@incubator.apache.org>]

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

Matthias Weßendorf updated ADFFACES-108:
----------------------------------------

    Affects Version/s: 1.0.1-incubating-core-SNAPSHOT

> Attribute map, scope maps and JSF 1.2
> -------------------------------------
>
>                 Key: ADFFACES-108
>                 URL: https://issues.apache.org/jira/browse/ADFFACES-108
>             Project: MyFaces ADF-Faces
>          Issue Type: Bug
>    Affects Versions: 1.0.1-incubating-core-SNAPSHOT
>            Reporter: Simon Lessard
>
> In Trinidad, RequestMap, SessionMap, ApplicationMap and AttributeMap use an <Object, Object> semantic. However, JSF 1.2 spec force <String, Object> so when Trinidad will be moving to the new version, some issues will have to be taken care of.
> Attribute map (from UIComponent.getAttribute) is a ValueMap instance in Trinidad. That map accept both String and PropertyKey keys. However, the PropertyKey option does not seem to be used anywhere
> ProcessUtils uses an Object key for the maxPathKey property that get registered in the session map.
> ColorConverter place the Object key named _PATTERN_WRITTEN_KEY inside the request map.
> For now, I'll only report bad usages of those maps, I won't fix them yet as there're more important issues. This bug entry should come very handly once we switch to 1.2 however.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.