My code from the Apache Camel Developer's Cookbook is now getting an error
trying to upgrade from Camel 2.15.2 to 2.15.3 around testing the Blueprint
Property / Test Support. This same code has worked fine over last 2 years
since version 2.12. With version 2.15.3, I'm seeing a runtime error
in
Cam
Hello,
I'm a Camel newbie looking for some help.
I'd like to know if is possible to start a camel spring route from an EJB
endpoint.
For example:
...
...
I'm getting the following exception when try to start the route:
"Caused by: java.lang.UnsupportedOperationException:
Is it advisable to store the messages in memory during redelivery for a
long time..if not can you please tell me what is the alternative...?
On Saturday, September 5, 2015, Claus Ibsen wrote:
> Yes Camel's error handler stores the messages in memory when it does
> waits to do redeliveries.
>
>
>
I tried having the sslContextPArameters tag outside the routes tag, but that
didn't help either. I now have my route as given below,
GET
Basic YWRtaW46dGVzdHBhc3M=
And i get this error,
Exhausted after delivery attempt: 1 caught:
javax.net.ssl.SSL
Looking closer at CamelBlueprintTestSupport line 240, its
doing getClass().getClassLoader().getResourceAsStream(descriptor) which I
believe is problematic as CamelBlueprintTestSupport and my blueprint
descriptors are in different bundles and therefore different class
loaders... Though I'd think the
Hi
Ah okay I found room for improvement
https://issues.apache.org/jira/browse/CAMEL-9115
You can try build from source and try 2.15.4-SNAPSHOT
On Sat, Sep 5, 2015 at 3:22 PM, Karts wrote:
> Our restConfiguration is as follows:
>
> />
>
> And we have Restlet simply as:
>
>
>
>
>
Our restConfiguration is as follows:
And we have Restlet simply as:
The war file sits in a Jetty 9 container.
Thanks
--
View this message in context:
http://camel.465427.n5.nabble.com/Stream-
Hi
Which http component do you use for rest-dsl and how is that setup?
Are you using servlet / jetty or restlet etc?
On Mon, Aug 31, 2015 at 10:35 PM, Karts wrote:
> Hi,
>
> We just upgraded to Camel 2.15.3 but this issue still remains unfortunately.
>
> Stack trace from 2.15.3 is below:
>
> jav
And btw jetty also supports producer, so you can use jetty instead of ahc.
On Sat, Sep 5, 2015 at 9:03 AM, Claus Ibsen wrote:
> Hi
>
> Ah the wait was part of the content path. Instead of you can
> build the url as a header with the key Exchange.HTTP_URI, then the ahc
> endpoint can be hardcoded
Hi
Ah the wait was part of the content path. Instead of you can
build the url as a header with the key Exchange.HTTP_URI, then the ahc
endpoint can be hardcoded and the header will be used as url instead
from the endpoint. Then you can reuse the endpoint/producers.
On Thu, Sep 3, 2015 at 5:21
10 matches
Mail list logo