Arbitrary signals with no interface about dbus-java HOT 3 CLOSED

I'm not so sure that it would be a good idea to allow 'null' as interface.

The reason why an interface is always expected is that the DBus spec says that signals must have an interface defined in the message header and one usually want to listen for a specific signal using a signal handler.

In case of the signal handlers, the code a bit further down will fail with NullPointerException.

Also the variable passed in to the handle() method of the interface will receive null...
Maybe there are more places where values are not checked for 'null' I'm not aware of yet.

Anyway, I don't know any other method than adding more if-statements to that already long list of if-statements.

from dbus-java.

Since the interface can never be null when sending, there's no way we can have a NullPointerException. This basically just allows you to match * for the interface, e.g. you don't care what the interface is, but you may care about what the member name is.

PR #65 contains my proposed changes.

from dbus-java.

I cleaned it a bit and merged your PR.

from dbus-java.