The various ObjectName constructors are explicitly documented to throw NullPointerException when one or more parameters are null. But in fact they throw MalformedObjectNameException.

Note that the TCK tests for this erroneous behaviour (bug 4943953) so it will need to be fixed at the same time as the RI.