Hi Karl,
sorry to answer you so late.
Anyway I full tested the code and it works properly.
I saw you use both the keys in the PostEvent message (UPnP.device.id and
upnp.deviceId) and I agree with you.
I've written a simple test code that allows to register and update EH
graphically.
At the moment you find it in my sandbox, I have still to understand how
to develop test case in mvn\Osgi, Marcel is working on it.
So I'm going to close the issue.
regards
francesco
ps:
again 4-3 ? ;-)
Francesco Furfari wrote:
Hi Karl,
I was disconnected this weekend.
I will try some test this evening or tomorrow
... of course my tests were erroneously based on the old keys too :-D
francesco
Karl Pauls wrote:
remind me to offer a beer next time you come in Italy ;-)
I look forward to it :-)
What I've realized is that EA subscriptions are limited respect the
tracking possibilities offered by the UPnP spec.
I just realized that there is another problem with this. The spec
requires that the events are published with upnp.serviceId and
upnp.deviceId keys... it follows that our approach with the filters
will not work because "upnp.serviceId" != UPnPService.ID and
"upnp.deviceId" != UPnPDevice.ID. I will commit a patch shortly that
fixes this by replacing all occurrences of mentioned keys in an
EventHandler filter with its UPnP counterpart. That way it should work
again. Would be great if you could test it sometime soon.
thanks
francesco
regards,
Karl
