DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15428>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15428 deluser [username], where username doesn't exist, gives an erroneous success message [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- OS/Version|Windows NT/2K |All Platform|PC |All ------- Additional Comments From [EMAIL PROTECTED] 2002-12-17 08:19 ------- It's actually a UserRepository interface problem, not an Avalon problem. If properly defined, removeUser would have a specified contract for non-existent users. It doesn't. So implementors are welcome to do nothing or throw a random RuntimeException if the user doesn't exist. The ObjectRepository is behaving in an acceptable fashion for the interface. Better options would've been to have the method return a boolean (true if the user was present/removed, false otherwise) or have a defined exception for this case. For the moment, a quick workaround is to have the RemoteManagerHandler check for existence of the user before calling users.removeUser. As I said, I've got a patch for this case now. We're revisiting the UsersRepository interface in 3.0, and this issue is sure to be addressed. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
