Makes sense to me. If we can simply do the null check, then we should not use UtilValidate.isNotEmpty() and increase the overhead.
+1 On Sat, Jun 18, 2016 at 10:13 AM, Pranay Pandey < pranay.pan...@hotwaxsystems.com> wrote: > +1 > > Best regards, > > Pranay Pandey > HotWax Systems > http://www.hotwaxsystems.com/ > > On Fri, Jun 17, 2016 at 8:00 PM, Ratnesh Upadhyay < > upadhyay.ratn...@gmail.com> wrote: > > > Hello community, > > > > There are lots of places in code where we have used > > UtilValidate.isNotEmpty() or UtilValidate.isEmpty() for GenericValue > object > > . GenericValue is never empty. Its always null or not null. So should we > > use directly null or not null check instead of UtilValidate.isNotEmpty() > > and UtilValidate.isEmpty() for GenericValue objects ? > > > > Basically these validation methods should preferably be used on Strings > or > > Lists and normal Maps. > > > > Thanks!! > > > > Regards, > > Ratnesh Upadhyay > > HotWax Systems | www.hotwaxsystems.com > > > -- Regards, Mohammad Kathawala Technical Consultant / Team Lead, Hotwax Systems, mohammad.kathaw...@hotwaxsystems.com <mohammad.kathaw...@hotwaxmedia.com>
