Mailing-List: contact dev-help@syncope.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@syncope.apache.org
MIME-Version: 1.0
Reply-To: coheigea@apache.org
In-Reply-To: <CD3FAF21-857B-4E06-8CCD-2494250C8AB7@apache.org>
References: <CAB8XdGCsDOH9_wNEsOp=hLCxu1n6FSSUnOfNeaY+R+=SCmXiKA@mail.gmail.com>
 <98b37986-671d-8099-11fe-d1917b0063b4@apache.org> <CAB8XdGCd6csEngEyk8ZUnj4vOuUUEKZ2T0pJ1BMgKbTfBjABbg@mail.gmail.com>
 <CD3FAF21-857B-4E06-8CCD-2494250C8AB7@apache.org>
From: Colm O hEigeartaigh <coheigea@apache.org>
Date: Wed, 21 Sep 2016 10:57:09 +0100
Message-ID: <CAB8XdGD8jCOtNyPr1ESzQvEecVXEqwCRPixAY_0oedOtEDP-Lg@mail.gmail.com>
Subject: Re: Syncope + Camel + Spring problem
To: "dev@syncope.apache.org" <dev@syncope.apache.org>
Content-Type: multipart/alternative; boundary=001a114b2ddc9437d1053d019120
archived-at: Wed, 21 Sep 2016 09:57:13 -0000

--001a114b2ddc9437d1053d019120
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Yep that works thanks! How is camelRoutesContext being picked up?

Colm.

On Tue, Sep 20, 2016 at 5:44 PM, Francesco Chicchiricc=C3=B2 <ilgrosso@apac=
he.org
> wrote:

> Il 20 settembre 2016 17:36:08 CEST, Colm O hEigeartaigh <
> coheigea@apache.org> ha scritto:
> >On Tue, Sep 20, 2016 at 4:02 PM, Francesco Chicchiricc=C3=B2
> ><ilgrosso@apache.org
> >> wrote:
> >
> >
> >> You could do:
> >>
> >>                 ApplicationContext appContext =3D new
> >> ClassPathXmlApplicationContext(
> >>                         new String[]{"camel-beans.xml"},
> >> ApplicationContextProvider.getApplicationContext());
> >>                 camelContext =3D new SpringCamelContext(appContext);
> >>
> >>
> >> e.g. setting the standard Syncope context as parent context.
> >>
> >
> >Yes this works fine to a point. The Camel component that I am calling
> >seems
> >to be picking up the bean definition from the configuration file +
> >working
> >correctly. However, I am getting a NPE subsequently in the Camel
> >Producers
> >in Syncope, caused by the fact that the Syncope PropagationManager in
> >PropagateComponent (which is @Autowired) is null. Does this ring any
> >bells?
>
> Hum, not really: you can alternatively leave the Java code as is, name
> your file camelRoutesContext.xml and place it in the classpath. It should
> work.
>
> Regards.
>
> >> It is not clear to me, however, how we could set up things to allow
> >such
> >> (very useful, indeed) possibility.
> >>
> >> An empty "camel-beans.xml" file (maybe camelEnv.xml would better
> >follow
> >> the naming in use) can be added under
> >>
> >> fit/core-reference/src/main/resources/all/
> >>
> >> and the code above could load it only when found.
> >> In this way the standalone distribution will simply provide the file
> >that
> >> anyone could start customizing, while for the Maven project the
> >reference
> >> guide [1] should be updated.
> >>
> >> WDYT?
> >>
> >> Regards.
> >>
> >> [1] https://syncope.apache.org/docs/reference-guide.html#enable-
> >> the-a-href-apache-camel-provisioning-manager-apache-
> >> camel-provisioning-manager-a
>
> --
> Francesco Chicchiricc=C3=B2
>
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
>
> Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF,
> OpenJPA, PonyMail
> http://home.apache.org/~ilgrosso/
>


--=20
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

--001a114b2ddc9437d1053d019120--