Hi Claus,
I tested with my two routes, and that works now without any problems.
Thanks,
Alfred
--
View this message in context:
http://camel.465427.n5.nabble.com/Mail-component-with-starttls-tp3409505p3415158.html
Sent from the Camel - Users mailing list archive at Nabble.com.
On Wed, Mar 9, 2011 at 10:01 AM, Alfred Hiebl wrote:
> Hi Claus,
>
> I tested with my two routes, and that works now without any problems.
>
Thanks. I have committed the patch to trunk. Will make it into Camel 2.7
> Thanks,
> Alfred
>
>
> --
> View this message in context:
> http://camel.46542
Hi
We have a ticket in JIRA to enhance the idempotent consumer EIP to
allow you to specify a sub-route what to do for duplicate messages.
Currently they are just ignored.
You should be able to use .end() when the idempotent consumer should
end, and then add an additional step. Then you can check
See this FAQ about using Camel in JBoss
http://camel.apache.org/how-do-i-run-activemq-and-camel-in-jboss.html
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Restlet-in-webapp-tp3415238p3415265.html
Sent from the Camel - Users mailing list archive at Nabble.com.
See this page about problem when using Nabble to post questions:
http://camel.apache.org/discussion-forums.html
--
View this message in context:
http://camel.465427.n5.nabble.com/Seda-VM-establishing-a-default-consumer-for-a-component-tp3413198p3415267.html
Sent from the Camel - Users mailing lis
Hello,
I'm using Camel with Servicemix and I have a hard time managing the test and
production server configurations for endpoints.
Is there a way to go in this cases?
I mean, I have different route details for test and production servers, so I
have to constantly pay attention when deploying.
And
Hi,
you should use properties for the endpoint urls or for parts of them.
Often it is also a good idea to split spring contexts into a fixed part
and a part that is different for the stages.
In the test project deploy your test properties in src/test/resources.
In the server then deploy your
A little unclear on what you expect here. The CamelContext does not
start because of an invalid endpoint. The only way to make it start
AFAIK would be to remove this invalid endpoint. I assume you are using
Spring. If you have control over when the spring application context
is constructed, you ca
thank you.
Is there any way I can access the list of producers and stop them at the end
of the route?
In such a way I will ensure I won't risk a high memory consumption if the
route will server thousands of distinct ftp servers (which could be the case
in the future)
--
View this message in conte
Hi,
Can you please provide further details regarding your issue.
1> Camel route details
2> Camel version and components involved.
3> Your current JVM heap settings etc
4> Garbage collection settings
Thanks,
Ashwin...
-
--
Hi all,
Unfortunately I'm only subscribed to this list - so I recognized the
announcement on the start page right now. That's my fault - but I like to
follow invitation for a comment at the end of the announcement.
First of all and to say it short - Camel is great and sure, developers
decide abou
Hi Bernd,
First of thanks for using camel and for taking the time to express your
thoughts. Much appreciated.
Comments inline.
Hadrian
On Mar 10, 2011, at 12:02 AM, bfischer wrote:
> Hi all,
>
> Unfortunately I'm only subscribed to this list - so I recognized the
> announcement on the start
On 3/10/11 7:02 AM, bfischer wrote:
Hi all,
Unfortunately I'm only subscribed to this list - so I recognized the
announcement on the start page right now. That's my fault - but I like to
follow invitation for a comment at the end of the announcement.
First of all and to say it short - Camel is
Hi,
I am using spring.
assuming the cxf endpoint is not a invalid endpoint, It is just not running
when the camelcontext starts.
what I want it's when camelcontext starts , it do not check the cxf endpoint
is started or not.
Just throws exception when I invoke cxf endpoint if the cxf server not
I'm not sure what your route looks like.
But according the stack trace, it looks like your cxf endpoint
configuration is wrong. It's better idea to let you know if the cxf
endpoint is wrong.
>org.apache.camel.FailedToCreateProducerException: Failed to create
Producer
> for endpoint: Endpoint
On Thu, Mar 10, 2011 at 12:44 AM, Hadrian Zbarcea wrote:
> Hi Bernd,
>
> First of thanks for using camel and for taking the time to express your
> thoughts. Much appreciated.
>
> Comments inline.
>
> Hadrian
>
> On Mar 10, 2011, at 12:02 AM, bfischer wrote:
>
>> Hi all,
>>
>> Unfortunately I'm on
16 matches
Mail list logo
