Mailing-List: contact users-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@felix.apache.org
From: David Jencks <david.a.jencks@gmail.com>
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: How to 'let the dust settle' with DS?
In-Reply-To: 
 <CALm0H55a=e3kFt8on-MbNZHJsNKHGN4rLr8Xksw=CbL6edUZvw@mail.gmail.com>
Date: Mon, 7 Sep 2015 21:58:58 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D56C773E-229F-430D-81D6-2C1B2C23BFBB@yahoo.com>
References: 
 <CALm0H54OiYwQtxBtBa1oeKrybtiyVm=aE1B0yhYg4-mpNtumNg@mail.gmail.com>
 <5FB3EC1F-B49D-4639-9DDF-A49374943DEB@yahoo.com>
 <CALm0H54rTzLr3WFvFGuW0v8aD9yBHX2sxoyaA7GMzCmHZ5dSkQ@mail.gmail.com>
 <A1215B9D-269C-48F8-BECB-BAEE6D5AA1D6@gmail.com>
 <6BFF2F6D-059C-43BE-AE09-93466A9E3914@yahoo.com>
 <CALm0H55D5j-E6erj65VZKvVcCe+8iwGZqYWFab9is4jSAuNJ_Q@mail.gmail.com>
 <C92F60F0-D2ED-4106-B1C7-52FBD3079C5D@yahoo.com>
 <CALm0H56uu3+R3r7Q1YG1bDgcyeHqnuwMNa2i-y8rErZ22xQy7Q@mail.gmail.com>
 <55EDCFBA.8040605@composent.com>
 <CALm0H56LhOB=iqAqefy5xA1BwXLmSShbRm7hTSzz3CgMW5bU7Q@mail.gmail.com>
 <D0D5EA47-4E6D-42EE-9823-87DF560CBDB0@yahoo.com>
 <CALm0H56BvccEQG32N7pM8OOKO9q58bsRL5PeLYnWRM40wUd4_w@mail.gmail.com>
 <275B9C64-E827-4FAD-9706-A749942F4BF9@yahoo.com>
 <CALm0H55a=e3kFt8on-MbNZHJsNKHGN4rLr8Xksw=CbL6edUZvw@mail.gmail.com>
To: users@felix.apache.org


> On Sep 7, 2015, at 8:07 PM, Benson Margulies <benson@basistech.com> =
wrote:
>=20
> The cardinality in the config admin does not seem to be sticking:
>=20
> @Component(configurationPolicy =3D ConfigurationPolicy.REQUIRE,
> configurationPid =3D "com.basistech.ws.worker")
>=20
> And:
>=20
> @Reference(cardinality =3D ReferenceCardinality.MULTIPLE, policyOption =
=3D
> ReferencePolicyOption.GREEDY)
> public void setWorkerComponentService(WorkerComponentService
> workerComponentService) {
>=20
> And in the relevant Karaf cfg file (com.basistech.ws.worker.cfg):
>=20
> # This is a DS property. It tells DS that there is one component
> service that we are consuming.
> WorkerComponentService.cardinality.minimum=3D1
>=20
> And the reference name in the DS metadata is WorkerComponentService.
>=20
> but the component goes ahead and activates when it has none (due to
> leaving out the component); the activation throws an exception due to
> my own code complaining.
>=20
> In spite of the exception thrown in the @Activate method, the
> component goes to REGISTERED, is there some particular exception that
> would prevent that?
>=20
> I have it working (up to the point of fun with Json deserialization
> from CXF, which is also working mostly) by putting the component in
> place, but eventually I need the constraint to hold things up; and it
> would be nice to have a way for an exception in activation to stop the
> train.

The spec says:

	=E2=80=A2 Once the component config- uration is deactivated or =
fails to activate due to an exception, SCR must unbind all the =
component's bound services and discard all references to the component =
instance associated with the activation.=20

Note that this doesn=E2=80=99t disable the component or unregister any =
services it may be exposing, because the exception may be highly =
transient, and e.g. the next time someone gets the service all may work =
smoothly and activate succeed.

I don=E2=80=99t know what version of ds you are =E2=80=9Cstuck=E2=80=9D =
with, at some point in the distant past I think that an exception on =
activation did something like disabling the component.  Due to all the =
cool new 1.3 features you should use the latest release 2.0 but the =
previous release may have also had the cardinality.minimum support=E2=80=A6=
 but don=E2=80=99t quote me :-)

thanks
david jencks


>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>=20


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org