How do I add options to the default Idempotent File Repository using the
Spring DSL?
Basically I want to change the "eager" option to false because it seems like
it will fix my issue of not inserting a name into the Repo if I set
Exchange.ROUTE_STOP = true.
But it seems the only way is to have a
Has anyone used Camel CDI in an OSGi environment? Does it work well or at
least OK there?
Brad
Hi Brad,
I’ve been working on Camel CDI in OSGi for a while and have ported my original
samples to be tested in Karaf, which can be found in [1]. These samples
exercise the portability of Camel CDI examples on OSGi, thus do not leverage
the SCR equivalent annotations that PAX CDI provides. So t
Hi Brad,
> On 21 Aug 2016, at 07:07, Brad Johnson wrote:
>
> When I look at the example provided I'm not entirely sure if I'm
> understanding how the CDI OSGi service mechanics work.
>
>@Produces
>@Named("sjms")
>@ApplicationScoped
> SjmsComponent sjms()
>
> I gather because it is
Hi Brad,
Camel CDI only works at the level of CDI beans, that is it won’t manage
RouteBuilder instances that are declared as SCR component.
Then you can imagine having Camel CDI and SCR components collaborating through
the OSGi registry, using PAX CDI in the mix.
That being said, Camel CDI / S
That's what gets a bit confusing about it all. I'm coming from Blueprint
which I've used for a few years now and very much like the automated wiring
provided by CDI and especially the ease of testing. But as I read about DS
and CDI it gets a bit confusing. Camel SCR probably can't work with CDI
Camel CDI is not based on Weld, it’s only the Camel CDI test facility which
relies on it for the JUnit runner as the simplest way to bootstrap a CDI
capable environment. You can quite easily achieve the same with Arquillian if
you need to target other kind of CDI environments, though Camel CDI t
Hi,
Osgiliath enterprise framework is using a combination of camel-cdi and
pax-cdi: it works pretty well ;).
Please take a look at this integration test module:
https://github.com/OsgiliathEnterprise/net.osgiliath.parent/tree/master/net.osgiliath.framework/net.osgiliath.features/net.osgiliath.fea
Antonin,
Ah, OK, that explains it. That's why I'm seeing Weld, it's just for the
unit tests. That's fine. The Camel CDI web page actually does say that
Karaf uses CDI 1.2 and pax-cdi so that now makes more sense.
Brad
On Mon, Aug 22, 2016 at 10:45 AM, Charlie Mordant
wrote:
> Hi,
>
> Osgiliat
>From my experience with SCR it is the weaker side of the equation. The CDI
seems to work just fine. I'd sort of looked at SCR initially as a way to
manage external services, references and properties while using CDI as the
internal bean and route building mechanism. But that seems a misfit righ
Cool. Thanks. That's perfect.
Brad
On Mon, Aug 22, 2016 at 10:22 AM, Antonin Stefanutti
wrote:
> Hi Brad,
>
> > On 21 Aug 2016, at 07:07, Brad Johnson
> wrote:
> >
> > When I look at the example provided I'm not entirely sure if I'm
> > understanding how the CDI OSGi service mechanics work.
>
On the surface both look very similar.
Whats the difference between the two? and when would you choose one
over the other?
Regards,
Rajith Muditha Attapattu
The routing slip method relies on a header to get the sequence, where
as with the DynamicRouter gives more flexibility by allowing a bean to
calculate the next step.
Apart from that are there any differences?
On Mon, Aug 22, 2016 at 2:30 PM, Rajith Muditha Attapattu
wrote:
> On the surface both l
Routing slip is calculated once and is therefore static.
Dynamic route is evaluated after each step and is therefore dynamic.
It keeps going on until the evaluation returns null / empty value.
On Mon, Aug 22, 2016 at 8:42 PM, Rajith Muditha Attapattu
wrote:
> The routing slip method relies on a
By the way, you may also want to compare those to a recipientList which is
fairly simple to use and can be used with pretty much any sort of variable.
http://camel.apache.org/recipient-list.html
For example, I've used it with a combined REST/SOAP interface in CXF to
route a request based on the
Yeah, my bad. I noticed that after I sent the link out. I may have been
thinking about the netty4 component but will refrain from comment as I
don't know if it does what you're looking for. But something must as your
request doesn't seem that unusual.
Brad
On Sun, Aug 21, 2016 at 11:39 AM, Jon
Hi
I just fixed the example so we wont forget to do it
https://github.com/apache/camel/commit/ba6fc872e40b48344330b7bc469892e63eb739cc
On Fri, Aug 19, 2016 at 10:08 AM, Claus Ibsen wrote:
> Hi
>
> Thanks for spotting.
>
> You are welcome to log a JIRA and provide a patch / github PR with a fix
>
Thank you Brad for the valuable info!
On Mon, Aug 22, 2016 at 3:06 PM, Brad Johnson
wrote:
> By the way, you may also want to compare those to a recipientList which is
> fairly simple to use and can be used with pretty much any sort of variable.
>
>
> http://camel.apache.org/recipient-list.html
>
Thank you Claus!
I just found out (the hard way) that I need to return null in the
dynamic router :)
On Mon, Aug 22, 2016 at 2:59 PM, Claus Ibsen wrote:
> Routing slip is calculated once and is therefore static.
>
> Dynamic route is evaluated after each step and is therefore dynamic.
> It keeps
Based on your lead I just added the pax-cdi-api and now have access to the
OSGiProvider API. That might be a good one to add to the camel-cdi
example. At this point I'm quite happy to just stick with the excellent
job done on the CDI and not bother with SCR or any from DS. If I recall
right Guil
By the way, I do confess some confusion about a bundle scoped OSGi
service. Seems that one can just use the regular injection in that case if
I'm understanding. In any case this gets me everything I want from easy
development with XML and easy unit tests and integration tests through Pax
Exam. E
Hi,
Please be kind enough to go through the following issue and provide
necessary support.
http://stackoverflow.com/questions/39076452/how-to-map-the-response-for-the-rest-request-by-apache-camel-http-component
Best Regards from
Udara Seneviratne
I am using Camel 2.16.0 and cxf 3.1.2
Here I'm trying to consume https service -
https://test.com:443/web-services/ship";
wsdlURL="wsdl/ShipService.wsdl"/>
Configured httpj bus within camel xml as below -
I am using Camel 2.16.0 and cxf 3.1.2
Here I'm trying to consume https service -
https://test.com:443/web-services/ship";
wsdlURL="wsdl/ShipService.wsdl"/>
Configured httpj bus within camel xml as below -
24 matches
Mail list logo