On Wed, Jul 26, 2017 at 4:28 PM, Francesco Chicchiriccò <[email protected] > wrote:
> This is more like a general approach, also taken for other cases where, > for example, it is requested to set values for attributes not allowed: log > a warning and discard. > > We might want to change this behavior, but then it will affect more than > just memberships. > OK - no let's just leave it as it is, for now anyway. > > Specifying the group name is more meant as a commodity when it is Syncope > to output MembershipTO instances: if you think this could be misleading, we > might remove the possibility to set the name via MembershipTO.Builder. > It is a bit misleading, but as the functionality is used when outputing MembershipTO instances as you say, let's just leave this as it is as well. Thanks, Colm. > > > Regards. > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Member at The Apache Software Foundation > Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail > http://home.apache.org/~ilgrosso/ > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
