You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Shawn McKinney (JIRA)" <ji...@apache.org> on 2016/01/09 01:09:39 UTC

[jira] [Created] (FC-135) Rename ambigous getter and setters names on User and UserAdminRole

Shawn McKinney created FC-135:
---------------------------------

             Summary: 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 <cl...@psu.edu> 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)