On 05/02/16 13:57, Claus Ibsen wrote:
On Mon, May 2, 2016 at 1:54 PM, Sven Bauhan <sven.bau...@ast.dfs.de> wrote:
I have context component to implement a protocol in our company.
As the success of a transmission depends a response from the receiver, it
has to be handled asynchronously.
On 05/02/16 13:57, Claus Ibsen wrote:
On Mon, May 2, 2016 at 1:54 PM, Sven Bauhan <sven.bau...@ast.dfs.de> wrote:
I have context component to implement a protocol in our company.
As the success of a transmission depends a response from the receiver, it
has to be handled asynchronously.
into the calling application
route.
On 05/02/16 13:48, Claus Ibsen wrote:
AsyncCallback is an implementation detail for component developers,
and the EIPs that are shipped in Camel.
What is your use-case?
On Mon, May 2, 2016 at 1:40 PM, Sven Bauhan <sven.bau...@ast.dfs.de> wrote:
On 04/29
On 04/29/16 21:29, Claus Ibsen wrote:
On Wed, Apr 27, 2016 at 10:05 PM, Sven Bauhan <sven.bau...@ast.dfs.de> wrote:
Hi,
I found the explanation for an AsyncProcessor:
http://camel.apache.org/asynchronous-processing.html
But I do not understand how to implement the corresponding AsyncCa
On 04/27/16 15:36, ravi narayanan wrote:
Hi Claus,
I tried implementing timeout aware aggregation strategy and implemented
timeout method in it.
now when ever timeout happens(complete Timeout/Partial Response) the Old
exchange message is coming to timeout method.
Of course it is the old
On 04/27/16 15:36, ravi narayanan wrote:
Hi Claus,
I tried implementing timeout aware aggregation strategy and implemented
timeout method in it.
now when ever timeout happens(complete Timeout/Partial Response) the Old
exchange message is coming to timeout method.
Of course it is the old
Hi,
I found the explanation for an AsyncProcessor:
http://camel.apache.org/asynchronous-processing.html
But I do not understand how to implement the corresponding AsyncCallback.
I did not find any example, how this can be done.
As the done() method just gets the boolean flag, I do not know how
Hi,
I am trying to implement a protocol (called ATS-M), which splits
messages for transportation and aggregates on receiving.
When the receiver gets correct segments, it returns response messages.
The sender waits for these response messages.
So it works asynchronously cause the sender cannot
Hi,
I have a problem using a seda queue when propagating an exception to a
caller route using errorHandler(noErrorHandler()).
What I want to achieve is to wait for a response message and sending an
exception to a caller route outside a camel context component, if no
response received within
Hi,
I have a problem with the current Camel version 2.16.2. In version
2.15.5 it works without problems.
--
I want to test the throwing of an exception when no response message is
received within a given timeout.
To create a timeout, I use multicast to clone the message and a
On 06/27/14 22:46, Sven Bauhan wrote:
Hi,
I want to use a Synchronisation in a route with an Aggregator.
So I implemented the onCompletion() method of the Synchronisation to
send a response that the message was received correctly.
My problem is that the onCompletion() method is called
Hi,
I want to use a Synchronisation in a route with an Aggregator.
So I implemented the onCompletion() method of the Synchronisation to
send a response that the message was received correctly.
My problem is that the onCompletion() method is called for each message
segment, not only for the
To explain my problem I provide the route in a diagram of my context
component.
It is composed by 2 main routes for the different message directions.
My problem is now, that I have to inform the aggregator, when the
message has left the route via the MESSAGE_OUT endpoint.
When the message can
Hi,
have a camel route to receive and decode incoming messages.
Sometimes it can happen the external application on destination endpoint
is not available. Then I get an exception which I can catch and send
back an error message.
If the received message is delivered correctly to the endpoint an
to the endpoint?
Thanks Sven
On 05/13/14 20:20, Sven Bauhan wrote:
Hi,
I have a route with a direct endpoint going to a socket connection. It
can be the the program on the other side of the connection crashes and
the connection is shut down. My messages in the route cannot be
delivered any
Hi,
I have a route with a direct endpoint going to a socket connection. It
can be the the program on the other side of the connection crashes and
the connection is shut down. My messages in the route cannot be
delivered any more. This happens especially from the aggregator in the
route.
In
On 08/26/13 16:43, Christian Posta wrote:
At the moment, there is a filtering writer that camel uses by default, and
unfortunately it's not configurable at the moment. If you open a JIRA i
will get a patch for you to make it configurable.
Hey thanks. I will open a ticket in Jira. But I need a
Hi,
as JAXB does not escape special characters when marshaling, there exists
a solution to use a special EscapingXMLStreamWriter (see
http://blog.lesc.se/2009/03/escape-illegal-characters-with-jaxb-xml.html).
I used this in combination with
org.apache.commons.lang.StringEscapeUtils to
I opened a bug report: https://issues.apache.org/jira/browse/CAMEL-6504
On 06/28/13 12:10, Christian Müller wrote:
I cannot look into the code yet, but I think this should be fixed. Feel
free to create a JIRA.
Best,
Christian
Sent from a mobile device
Am 28.06.2013 10:54 schrieb Sven Bauhan
Hi,
I think I found a bug in org.apache.camel.main.Main#doStop():
When I call a Camel application with parameter -h all parameters are
printed an the program exits.
But it is no clean exit; it throws an java.lang.IndexOutOfBoundsException.
The reason for this is the expression in doStop():
+
Hi,
I wonder if there is a Camel endpoint for ONC-RPC (also called SUN RPC).
I found endpoints for XML-RPC and SOAP but no one for ONC-RPC
Can someone tell me, if such an endpoint exist or is planned?
Perhaps I could use one protocol definition in Apache MINA, but I did
not find it there
Ok, new issue: https://issues.apache.org/jira/browse/CAMEL-6325
On 04/27/13 08:06, Claus Ibsen wrote:
Hi
Yeah that may be possible. Feel free to log a JIRA ticket.
On Fri, Apr 26, 2013 at 6:33 PM, Sven Bauhan s...@ast.dfs.de wrote:
Ok, but then the timeout for the aggregation can occur
Hi,
I try to implement a fault handling in my AggregationStrategy for
missing segments or a wrong sequence order.
The standard for my protocol says, when the segments are not received in
correct order, the receiver shall send an error response and withdraw
all previously received segments
You can just store some state on the oldExchange before throwing that
exception in the aggregate method.
So the next time, you can find that state on oldExchange and then
regard it as null.
On Fri, Apr 26, 2013 at 3:49 PM, Sven Bauhan sven.bau...@ast.dfs.de wrote:
Hi,
I try to implement
then its not
completed yet.
On Thu, Apr 18, 2013 at 12:25 PM, Sven Bauhan sven.bau...@ast.dfs.de wrote:
Hi,
I use an aggregator to combine segmented messages (as the channel has
limited size).
For each received segment a response message is expected with the
appropriate response status.
As correlation
Hi,
I try to understand how to handle with errors in messages within a camel
route.
I have the following route in a Camel context component:
FailureReceiveProcessor fails = new FailureReceiveProcessor();
onException(MessageReceiveException.class).handled(false).process(fails);
Hi,
I use an aggregator to combine segmented messages (as the channel has
limited size).
For each received segment a response message is expected with the
appropriate response status.
As correlation key the message ID is used; and each segment has a
segment number.
When a complete message
Hi,
I think for the interface Registry a method bind() should be defined.
Here comes the explanation why:
Finally I managed to create a camel context component to put a route in
a black box. But I want to put this context component into a library and
hide it behind an API.
Starting point
use the DefaultCamelContext to define your own context,
with it's own name as this one is blackbox, and it's own routes.
Taariq
On Mon, Mar 11, 2013 at 11:21 AM, Sven Bauhan s...@ast.dfs.de wrote:
On 03/09/13 20:40, Henryk Konsek wrote:
Hi Sven,
I'm trying to build my own context component
On 03/13/13 12:50, Taariq Levack wrote:
I got the idea that you really want to define an instance of the
DefaultCamelContext, and not the new class/implementation that you are
asking about.
I did not mean to create a new implementation of DefaultCamelContext. I
want to create a class for a
On 03/09/13 20:40, Henryk Konsek wrote:
Hi Sven,
I'm trying to build my own context component as described in
http://camel.apache.org/context.html.
Actually Context Component is ready to use out of the box. You don't
need to create your own. Or if you have to, please share with us the
On 03/10/13 02:53, Christian Müller wrote:
Can you explain in more detail what you want to do? I didn't understand
your requirement...
I have to implement a protocol called ATS-M. It splits messages into
segments for transmission. At the receiver the segments are aggregated
to the original
not make sense for
a context component.
Is there a better interface for this? Or should i create my own class
without interface?
Thanks,
Sven Bauhan
automatically (JAXB)?
Thanks,
Sven Bauhan
34 matches
Mail list logo
