Quick question related to LDAP filter format used by generic capabilities and requirements:
If bundle A provides a list of capabilities that a client can be interested in individually, is it necessary to have a separate capability for each, e.g. Provide-Capability: com.acme.foo; cap=cap1, com.acme.foo; cap=cap2, com.acme.foo; cap=cap3 Or can this be combined into a single capability with a list? How would a filter look like to find an individual capability cap2 in the list? Provide-Capability: com.acme.foo; cap:List<String>=cap1,cap2,cap3 Thanks, Tim.
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
