Does anyone see why this would not be working?
@Reference(
cardinality = ReferenceCardinality.MULTIPLE,
name = MBean,
policy = ReferencePolicy.DYNAMIC,
policyOption = ReferencePolicyOption.GREEDY,
target =
From: Raymond Auge raymond.a...@liferay.com
K, so it can't handled Object (or the anything case)?
DS can handle any type a service is registered under including
java.lang.Object. But it does require you tell DS the service type (either
in the interface element if you write the XML or in the
From: Raymond Auge raymond.a...@liferay.com
On Mon, Mar 30, 2015 at 2:41 PM, BJ Hargrave hargr...@us.ibm.com
wrote:
From: Raymond Auge raymond.a...@liferay.com
K, so it can't handled Object (or the anything case)?
DS can handle any type a service is registered under including
K, so it can't handled Object (or the anything case)?
ok! not a problem.
- Ray
On Mon, Mar 30, 2015 at 2:11 PM, BJ Hargrave hargr...@us.ibm.com wrote:
From: Raymond Auge raymond.a...@liferay.com
Does anyone see why this would not be working?
@Reference(
I'll assume this is the
On Mon, Mar 30, 2015 at 2:41 PM, BJ Hargrave hargr...@us.ibm.com wrote:
From: Raymond Auge raymond.a...@liferay.com
K, so it can't handled Object (or the anything case)?
DS can handle any type a service is registered under including
java.lang.Object. But it does require you tell DS the
From: Raymond Auge raymond.a...@liferay.com
Does anyone see why this would not be working?
@Reference(
I'll assume this is the OSGi annotation.
cardinality = ReferenceCardinality.MULTIPLE,
name = MBean,
policy = ReferencePolicy.DYNAMIC,
policyOption =
When you use the ServiceReference style of bind, bnd can’t rely on the
signature of the bind method to ascertain the service type you want. Hence you
have to add an extra hint by using the ‘service’ attribute.
It’s probably a bit dim for bnd to assume that we are binding to services of
type
