Agemo Cui wrote:
*No, * * I don't think so unless the names of those
sub-interfaces/sub-classes * *are also used to register the service.
And then you can create a complicate fiter like
"(|(objectClass=xxxxx)(objectClass=xxxxx))". If the prefix of the
interfaces are the same, then the filter could be easy to create like
"(objectClass=xxxx.xxxx.xxx.SameName*)"* * by using wildcard. *
I've seen that the filter doesn't actually check that the Service is an
istance of superclass/interface
specified in the filter (i.e. the listener does NOT get notified when
services implementing
subclasses/subinterfaces change their state).
Going with the package prefix "hack" solves some of my issues, but has
some major drawbacks:
1) I can't safely downcast the service object to an interface if the
containing package contains
more than one interface
2) I can't force other developers from implementing my interfaces in
their preferred packages,
making my listener "deaf".
I'll see tomorrow how to manage this issue (maybe a custom service
property)
as it's getting late here in Italy.
Regards,
--
Logo
Guido Spadotto
Soluta.net, Italy
http://www.soluta.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
