The nullValue() method would stay. I'm talking about the nullObject() methods, which create objects of any type that return null values for all methods.
Sent from my iPad On Jul 26, 2013, at 11:33 PM, Matt Benson <gudnabr...@gmail.com> wrote: > I know I have used the #nullValue() utility method elsewhere before, so I'd > prefer the latter option, or in the case of the former to provide a similar > method in [lang]. > > Matt > On Jul 26, 2013 10:26 PM, "James Carman" <james_car...@gap.com> wrote: > >> We currently have some package cycles according to Sonar. The >> org.apache.commons.proxy2 (I'm working in the branch) package depends on >> the org.apache.commons.proxy2.interceptor package (and vice versa) because >> of its use of the NullInvoker class to create "null objects." Since we >> have a little bit of leeway here (we're bumping major versions), we have >> the opportunity to clean this up. Perhaps we remove the utility methods >> from ProxyUtils (we aren't using it)? Perhaps we just make NullInvoker a >> private static inner class of ProxyUtils and keep the utility methods? >> What say you? >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
