The mandatory reference:
VpnRemotes vpnRemotes = null;
@Reference(policyOption = ReferencePolicyOption.GREEDY)
public void setVpnRemotes(final VpnRemotes vpnRemotes) {
this.vpnRemotes = vpnRemotes;
}
The optional reference:
private final Set<VpnRemotesClient> clients = new CopyOnWriteArraySet<>();
@Reference(policyOption = ReferencePolicyOption.GREEDY, policy =
ReferencePolicy.DYNAMIC,
cardinality = ReferenceCardinality.MULTIPLE)
public void addVPNRemotesClient(final VpnRemotesClient client) {
this.clients.add(client);
}
public void removeVPNRemotesClient(final VpnRemotesClient client) {
this.clients.remove(client);
}
F.
On 12/05/16 18:09, David Jencks wrote:
Can you verify that your case is the same as Victor’s? All the circular
references I encounter work fine, if there are 2 different broken cases that
would be good to know when investigating Victor’s case.
thanks
david jencks
On May 12, 2016, at 2:58 AM, Ferry Huberts <[email protected]> wrote:
On 12/05/16 11:55, Victor Antonovich wrote:
12.05.2016 12:42, Ferry Huberts wrote:
Hi,
I'm seeing log lines like:
[some.component(17)] Circular reference detected, getService returning
null
These are invalid for my application since one end of the relation is
mandatory and the other end is optional.
DS should not complain in this way when at least one end of the relation
is optional.
(I can't file an issue on this since JIRA seems to be in some kind of
lockdown)
Fyi, this issue already has been filed a while ago:
https://issues.apache.org/jira/browse/FELIX-4417
ok, tnx
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
<mailto:[email protected]>
For additional commands, e-mail: [email protected]
<mailto:[email protected]>
--
Ferry Huberts
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
