DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=36886>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36886





------- Additional Comments From dj-jogi@web.de  2005-10-02 19:38 -------
Hm, but there would be little difference in the use of
Validate.notNull(Object,String) and the Methods notEmpty with take an message as
second argument. At the moment I write something like:

public void foo(Object bar){
  Validate.notNull(bar, "bar was null");
  //other code
}


But if notNull would throw an NullArgumentException you should write 

public void foo(Object bar){
  Validate.notNull(bar, "bar");
  //other code
}

Or you would get "bar was null must not be null." as message. :-)


BTW: Perhaps I want to provide some methods to this class (Validate). What do I
have to do? (Or should I create an issue for every new method?)

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org