[
https://issues.apache.org/jira/browse/FC-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney resolved FC-135.
-------------------------------
Resolution: Fixed
> Rename ambigous getter and setters names on User and UserAdminRole
> ------------------------------------------------------------------
>
> Key: FC-135
> URL: https://issues.apache.org/jira/browse/FC-135
> Project: FORTRESS
> Issue Type: Improvement
> Affects Versions: 1.0.0-RC40
> Reporter: Shawn McKinney
> Fix For: 1.0.0-RC41
>
>
> Ticket was a request from Chris Pike:
> On Jan 5, 2016, at 10:35 AM, Chris Pike <[email protected]> wrote:
> There are a couple instances where models have multiple set methods for the
> same field.
> UserAdminRole has...
> public void setOsP( String osP )
> public void setOsP( Set<String> osPs )
> public void setOsU( Set<String> osUs )
> public void setOsU( String osU )
> User has...
> public void setRole( String roleName )
> public void setRole( UserRole role )
> public void setAdminRole( UserAdminRole role )
> public void setAdminRole( String roleName )
> This is causing some issues down the line with jackson. I have a workaround
> but wanted to see if there was any possibility of changing one of the method
> names.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
