Thank you for your comments, Simon and BJ. I got it.
Best Regards, Ikuo On Thu, 20 Aug 2009 08:30:33 -0400 BJ Hargrave <[email protected]> wrote: BJ> null is not a valid argument. So some sort of RuntimeException will be BJ> thrown. Likely NPE but could also be IllegalArgumentException depending BJ> upon how CM is implemented. BJ> -- BJ> BJ> BJ Hargrave BJ> Senior Technical Staff Member, IBM BJ> OSGi Fellow and CTO of the OSGi Alliance BJ> [email protected] BJ> BJ> office: +1 386 848 1781 BJ> mobile: +1 386 848 3788 BJ> BJ> BJ> BJ> BJ> From: BJ> Ikuo Yamasaki <[email protected]> BJ> To: BJ> OSGi Developer Mail List <[email protected]> BJ> Date: BJ> 2009/08/19 21:46 BJ> Subject: BJ> [osgi-dev] conf.update(null) BJ> Sent by: BJ> [email protected] BJ> BJ> BJ> BJ> Hi all, BJ> BJ> Is the following my understanding correct ? BJ> BJ> ------------------ BJ> The caller of update(Dictionary props) method of Configuraion object BJ> should confirm props is not null in advance or try/catch BJ> NullPointerException. BJ> BJ> In other words, the caller Should expect update(null) throws BJ> NullPointerException. BJ> BJ> ------------------ BJ> Similar argument I found before AFAIK was BJ> BundleContext#getService(ServiceReference reference) is called with the BJ> reference of null(NullPointerException will be thrown). BJ> BJ> Generally speaking, the caller should expect NullPointerException in BJ> case that the argument is Object and javadoc doesn't describe anything BJ> in case of null. BJ> BJ> Best regards, BJ> BJ> --------------------- BJ> NTT Cyber Solutions Laboratories BJ> BJ> Ikuo YAMASAKI BJ> E-mail: [email protected] BJ> TEL +81-46-859-8537 FAX +81-46-855-1282 BJ> BJ> BJ> _______________________________________________ BJ> OSGi Developer Mail List BJ> [email protected] BJ> https://mail.osgi.org/mailman/listinfo/osgi-dev BJ> _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
