Re: expectedMessageCount is not considered

2016-02-19 Thread Claus Ibsen
The expectedBodyReceived will override the count, where you set only 1 body and hence 1 message received. If you want to expect that all message bodies contains okay, then use .allMessages().body(). instead On Sat, Feb 20, 2016 at 12:13 AM, zappee wrote: > Hi, > > How can I set the value of the

Re: Usage of properties in datasource definition - Please help

2016-02-19 Thread Claus Ibsen
The is spring handling those, so setup spring property placeholders to let it does its work there. Camel's property placeholder is from whats inside . You can bridge the two of them. See more details in the camel website On Fri, Feb 19, 2016 at 11:38 PM, Launcelot wrote: > I have a property fil

Re: Usage of properties in datasource definition - Please help

2016-02-19 Thread Grzegorz Grzybek
HI Launcelot I see you're using Spring XML. Camel's element is used to resolve placeholders in Camel elements (like URIs). However, in order to have your ${db.pass} replaced, you have to enable Spring's own property placeholder. See here: http://docs.spring.io/spring/docs/current/spring-framework

expectedMessageCount is not considered

2016-02-19 Thread zappee
Hi, How can I set the value of the expected message count? In my test scenario it is set to 200 but I got a Expected: <1> but was: <0> instead of Expected: <200> but was: <0> MockEndpoint resultEndpoint = getMockEndpoint(ENDPOINT_URL); resultEndpoint.expectedMessageCount(200); resultEndpoint.ex

Re: cxf:bean doesn't resolve properties with CamelBlueprintTestSupport

2016-02-19 Thread Brad Johnson
I just use one full copy of properties for tests and another that I include in the bundle. If you don't put a camel context in the porperties then you don't end up with multiple contexts and OSGi/karaf automatically pick up all the blueprint files it finds in your OSGI-INF blueprint folders. So I

Re: cxf:bean doesn't resolve properties with CamelBlueprintTestSupport

2016-02-19 Thread Ephemeris Lappis
Hello. Indeed, it seems to work with Camel 2.16.2. As I've explained in my previous reply, I've refactored the blueprints to extract in separated files the roots that have unresolved properties. This will allow us to test all the important blueprints with the targeted version of Camel. An explanati

Re: cxf:bean doesn't resolve properties with CamelBlueprintTestSupport

2016-02-19 Thread Ephemeris Lappis
Hello. Happy to see I'm not the only one getting such a problem ! I've also modified the blueprints to put the entry routes that are configured with these problematical properties in a separted file that needs no real unit tests, and all the routes that are to be actually tested in other blueprin

Usage of properties in datasource definition - Please help

2016-02-19 Thread Launcelot
I have a property file defined as follows http://camel.apache.org/schema/spring";> db.properties has a property in it which contains db.pass=valuesnipped I have a datasource definition as under

Re: Camel and CDI moving from CdiCamelContext to CamelContext

2016-02-19 Thread Agusti Tomas
Hi, Yes, this helps. I'll try again with CdiCamelContext. Thanks! On Fri, Feb 19, 2016, 20:43 Antonin Stefanutti wrote: > > > On 19 Feb 2016, at 19:37, Agusti Tomas wrote: > > > > I am new to Camel and relatively new to mailing lists so apologies in > > advance if I don't stick to the rules.

Re: Camel and CDI moving from CdiCamelContext to CamelContext

2016-02-19 Thread Antonin Stefanutti
> On 19 Feb 2016, at 19:37, Agusti Tomas wrote: > > I am new to Camel and relatively new to mailing lists so apologies in > advance if I don't stick to the rules. Constructive feedback is always > welcome and I'm a fast learner! We’re here to help :) > So I am moving from JBoss EAP 6.1 to 6.4

Re: Invoking Dynamic OSGi Blueprint services from a Java RouteBuilder

2016-02-19 Thread Brad Johnson
Good point. I guess I was just running through in my head what I did when I ran into the problem. There's definitely a classloader difference depending on how the routes and injection get set up. I have some speculations about it but that's all. I wish I had more time to chase it down. On Fri,

Camel and CDI moving from CdiCamelContext to CamelContext

2016-02-19 Thread Agusti Tomas
Hello everybody, I am new to Camel and relatively new to mailing lists so apologies in advance if I don't stick to the rules. Constructive feedback is always welcome and I'm a fast learner! So I am moving from JBoss EAP 6.1 to 6.4 and installing Fuse 6.2.1 on top. I was using 2.15.1 before the mo

Re: Is there a way to selectively disable data binding in a rest-dsl route?

2016-02-19 Thread Matt Sicker
Thanks Claus! On 19 February 2016 at 12:11, Claus Ibsen wrote: > Hi > > Ah yeah we should support that. I logged a ticket > https://issues.apache.org/jira/browse/CAMEL-9625 > > On Fri, Feb 19, 2016 at 6:01 PM, Matt Sicker wrote: > > I tried doing that and it still marshals the output (which is

Re: Is there a way to selectively disable data binding in a rest-dsl route?

2016-02-19 Thread Claus Ibsen
Hi Ah yeah we should support that. I logged a ticket https://issues.apache.org/jira/browse/CAMEL-9625 On Fri, Feb 19, 2016 at 6:01 PM, Matt Sicker wrote: > I tried doing that and it still marshals the output (which is a > ByteArrayInputStream object) into a base64-encoded version of the stream >

Re: cxf:bean doesn't resolve properties with CamelBlueprintTestSupport

2016-02-19 Thread Quinn Stevenson
Looks like something was fixed in 2.16.2 - I tried your sample and if I change the Camel version to 2.16.2, your test passes. > On Feb 19, 2016, at 4:28 AM, Ephemeris Lappis > wrote: > > Hello again. > > I've build a simple project with simple routes to test the property > restitution (the Z

Re: Invoking Dynamic OSGi Blueprint services from a Java RouteBuilder

2016-02-19 Thread Quinn Stevenson
No - I haven’t tried logging the class type. I know it’s not a proxy because I don’t get a ServiceTimeoutException when the service is unavailable. I guess it could be a broken proxy, but I doubt it. I’ll try a couple of things and post my results. > On Feb 18, 2016, at 3:24 PM, Brad Johnson

Re: cxf:bean doesn't resolve properties with CamelBlueprintTestSupport

2016-02-19 Thread Brad Johnson
I've always had problems with using cfg files in CBTS and don't know exactly why. I think it may be a loading life cycle issue. For example, in using CXF I'll commonly specify the service class in the configuration file. What I'v resorted to doing is using multiple blueprint files. Blueprint for

Re: Is there a way to selectively disable data binding in a rest-dsl route?

2016-02-19 Thread Matt Sicker
I tried doing that and it still marshals the output (which is a ByteArrayInputStream object) into a base64-encoded version of the stream surrounded by double quotes. On 19 February 2016 at 10:21, Matt Sicker wrote: > So I could just specify in.setHeader(Exchange.CONTENT_TYPE, > "application/vnd.

Re: cxfrs swagger

2016-02-19 Thread camel_case
Just to clarify, I could use swagger with cxf, but not cxfrs and camel? Is there no work around using the cxf with swagger examples to let swagger know about the route url by assignment as in the example below ( so far as I tried this, trouble of this nature: Caused by: java.lang.ClassCastExcepti

Re: Is there a way to selectively disable data binding in a rest-dsl route?

2016-02-19 Thread Matt Sicker
So I could just specify in.setHeader(Exchange.CONTENT_TYPE, "application/vnd.apple.pkpass") and it won't get marshalled? On 19 February 2016 at 00:45, Claus Ibsen wrote: > Set a different content-type as binary is not json then. > > On Thu, Feb 18, 2016 at 9:45 PM, Matt Sicker wrote: > > Most o

Outlook Rest API Camel Component

2016-02-19 Thread kag
Hi there, I've been googling a little bit about how to extract calandar events from an outlook calendar. Basically we would like to be able to sync between outlook calendars and a couple of less known calendar systems. Microsoft provides an Outlook Calendar Rest API. What it the best way to appr

Re: received ICLA

2016-02-19 Thread Claus Ibsen
Already responded 2 days ago to this http://camel.465427.n5.nabble.com/received-ICLA-td597.html On Fri, Feb 19, 2016 at 3:45 PM, mary mistretta wrote: > I haven't heard back about this yet from the dev list, so I am sending to > the user list to confirm I followed the correct process. > > Tha

Fwd: received ICLA

2016-02-19 Thread mary mistretta
I haven't heard back about this yet from the dev list, so I am sending to the user list to confirm I followed the correct process. Thanks, Mary Cochran (Mistretta) -- Forwarded message -- From: mary mistretta Date: Tue, Feb 16, 2016 at 12:42 PM Subject: received ICLA To: d...@cam

Re: Get Socket Status of Netty4 Route

2016-02-19 Thread Leomar
Hi there, i found a suitable solution for my usecase. In the netty 4 endpoint there is a encoder option to add ChannelHander to the endpoint. So i wrote a io.netty.channel.ChannelDuplexHandler extension. This Handler will now be called in cased of connection events for the Netty channel. Using

Apache camel in simpl4

2016-02-19 Thread jro_simpl4
Hello, i am a new member in the apache camel user group, and I want to let you know of our camel-related project simpl4, an open source development environment, which is licensed under the GPL v3. Routes can be edited with an graphical edior, as well as the most other parts (mainly BPMN2) in the s

Re: cxf:bean doesn't resolve properties with CamelBlueprintTestSupport

2016-02-19 Thread Ephemeris Lappis
Hello again. I've build a simple project with simple routes to test the property restitution (the ZIP is attached). The blueprint and its configuration file work as expected deployed on my ServiceMix 6.1.0 that comes with Camel 2.16.1 as my unit tests. The file "error-2_16_1.txt" is a copy of the

InvalidPayloadException: No body available

2016-02-19 Thread hoboy
I have the following 2 files. Jax-rs @ApplicationPath("Test") public class ApplicationActivator extends Application { } and the resource class @Path("test") public class MyResource { @Context UriInfo uri; @Context HttpHeaders headers; @GET

Re: cxf:bean doesn't resolve properties with CamelBlueprintTestSupport

2016-02-19 Thread Ephemeris Lappis
Hello. I've done more tests, and I have two comments. 1) The error also occurs on other endpoint type. for example, if I use the same property on a direct option, the route construction fails with the same exception. This means that this is not a CXF specific problem... 2) I've seen a message in