[jira] [Commented] (SYNCOPE-1106) Remove misleading getAttrMap and similar methods from TOs

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (SYNCOPE-1106) Remove misleading getAttrMap and similar methods from TOs

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SYNCOPE-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046708#comment-16046708 ]

ASF subversion and git services commented on SYNCOPE-1106:
----------------------------------------------------------

Commit 84313c2e6fb9dacf8b399a18640eab1ff538de4f in syncope's branch refs/heads/2_0_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=84313c2 ]

[SYNCOPE-1106] Updating docs


> Remove misleading getAttrMap and similar methods from TOs
> ---------------------------------------------------------
>
>                 Key: SYNCOPE-1106
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1106
>             Project: Syncope
>          Issue Type: Improvement
>          Components: common
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>             Fix For: 2.0.4, 2.1.0
>
>
> {{ConnObjectTO}} and the classes implementing {{AttributableTO}} provide methods like as {{getAttrMap()}}, {{getPlainAttrMap()}}, {{getDerAttrMap()}} and {{getVirAttrMap()}}, with purpose of providing a read-only view of all attributes (of different types).
> Using such methods, however, can be costing (the resulting map is built for each invocation) and also confusing, as one would expect that adding / removing entries would result into effective attribute changes.
> Such methods should be removed, and substituted with more tailored replacements where needed.



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