Issue TTWS44 has just been modified by user quintonm
You can view the issue detail at the following URL:
<http://scarab.werken.com/scarab/issues/id/TTWS44>
The following modifications were made to this issue:
I don't agree that renameUser() is the best method. most people use the DB security
service. Those users are using turbineUser like a normal torque object. No other
torque object has this limitation.
I really don't like the LDAP service throwing an exception if the DB version does not.
This will make people who try to move to the LDAP version think that it is broken if
they don't notice that little bit of information in the documentation.
Since most people will use the database version, I am more concerned about it. I
would like to see users simply modify the username and call the save() method. If
this simply can not be done in LDAP because of the primary key used there, then have
the save() implementation for LDAP call renameUser(). If that can not be done, throw
an exception.
Just my 2 cents.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
