Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
From: Quinn Stevenson <quinn@pronoia-solutions.com>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_485C4BE3-522F-4054-9561-4AE9FE7BEAFA"
Message-Id: <92F068F3-5964-4446-9F0D-D08980C342EB@pronoia-solutions.com>
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: Potential Bug in CamelBlueprintTestSupport
Date: Wed, 6 Jan 2016 14:35:49 -0700
References: <D870E62C-D590-4722-83C3-40C514C1B60B@pronoia-solutions.com>
 <CAAdXmhqZPr7ZR_gemdvQ5ezEaxQ70A4P5yX6gOda=Brf6XxwNg@mail.gmail.com>
To: dev@camel.apache.org
In-Reply-To: 
 <CAAdXmhqZPr7ZR_gemdvQ5ezEaxQ70A4P5yX6gOda=Brf6XxwNg@mail.gmail.com>

--Apple-Mail=_485C4BE3-522F-4054-9561-4AE9FE7BEAFA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Grzegorz -

Thank you for the link - I=E2=80=99ve read through it many times - it is =
very very helpful.  =46rom what I understand, this should work - the =
location of the blueprint file shouldn=E2=80=99t effect the way the test =
runs, should it?  Maybe I=E2=80=99m missing something simple.

It looks like my unit test attachment didn=E2=80=99t come through. Sorry =
- I didn=E2=80=99t think about the mailing list filtering out =
attachments.  You can get to the test here =
https://github.com/hqstevenson/camel-blueprint-test-properties.git =
<https://github.com/hqstevenson/camel-blueprint-test-properties.git>=20

I've been testing this primary against 2.17-SNAPSHOT, but I=E2=80=99ve =
tested against several versions.  The POM for the unit test has the =
versions listed that I tested, but I was messing with the test a little =
so I=E2=80=99m not sure the list is completely accurate.  I=E2=80=99ll =
verify those and update the POM if needed.

Quinn Stevenson


> On Jan 6, 2016, at 12:21 PM, Grzegorz Grzybek <gr.grzybek@gmail.com> =
wrote:
>=20
> Hello Quinn
>=20
> What Camel version do you use? I wrote a thorough explanation of
> CamelTestBlueprint and the changes we've made to how tests are
> performed and synchronized.
> Here: =
http://ggrzybek.blogspot.com/2015/12/camel-blueprint-test-support.html
> You can find there links to JIRA issues describing exactly the same
> problems you have with `update-strategy=3D"reload"`.
>=20
> best regards
> Grzegorz Grzybek
>=20
> 2016-01-06 19:16 GMT+01:00 Quinn Stevenson =
<quinn@pronoia-solutions.com>:
>> I=E2=80=99ve encountered an issue, but I=E2=80=99m not sure if this =
is a bug or a user error.
>>=20
>> I=E2=80=99m trying to write some tests using =
CamelBlueprintTestSupport for bundles where the blueprint file is in =
src/main/resources/OSGI-INF/blueprint.  However, I=E2=80=99m getting =
random failures in the test on startup.
>>=20
>> I=E2=80=99ve narrowed it down to using update-strategy =3D =
=E2=80=9Creload=E2=80=9D and overriding properties in the test.  The =
tests fail (most of the time) when the actual blueprint file is in =
src/main/resources/OSGI-INF/blueprint.  Even when the test doesn=E2=80=99t=
 fail, you=E2=80=99ll see multiple camel contexts get created during the =
test, while the test this is based on from camel-test-blueprint only =
creates two camel contexts.
>>=20
>> However, if I move the blueprint file to =
src/test/resources/OSGI-INF/blueprint, the test passes.
>>=20
>> Since I need the blueprint packaged in the bundle in =
OSGI-INF/blueprint, I can=E2=80=99t move the blueprint file to the =
src/test/=E2=80=A6 area.
>>=20
>> Is there another way I should be testing this sort of thing?
>>=20
>> I=E2=80=99ve created a unit test based on the =
ConfigAdminLoadConfigurationFileAndOverrideTest from the =
camel-test-blueprint module that demonstrates the issue.
>>=20
>>=20
>>=20
>>=20
>> Quinn Stevenson
>>=20
>>=20
>>=20
>>=20


--Apple-Mail=_485C4BE3-522F-4054-9561-4AE9FE7BEAFA--