So, basically, there is no concept of consumer endpoint: an exchange
is sent from a component to an endpoint. Inside servicemix
components, we usually have this concept of consumer endpoint, but in
such case, this means that the component has to dispatch the incoming
exchange back to the endpoint
HI Guillaume
I hope you are right even though I am not quite sure how you want to
figure out the service name of the consumer. I still think it is a
problem of the core. Even if we can fix the problem inside the Bean BC
the problem may arise on other BCs as well. I think that we should not
only
I had some time to look at your test case on the plane and i think i
found a fix. In all cases i'm quite sure that the problem comes from
the component and not from the container. The fix is mainly to inject
on the pojo a delivery channel that will track consumer exchanges sent
by the bean. That
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tomorrow I plan to try to fix this issue but if anyone sees a flaw in
my design please stop beforehand.
Today I finally resolved the problem of how does ServiceMix know to
which component it should send the Message Exchange (ME) back even
Hi Geeks
I am moving this thread to the DEV mailing list because it not about
using ServiceMix anymore. The problem is that when using the
asynchronous message exchange that the response is not sent back to
the calling SU but to the Provider Endpoint of the called SU.
I just keep on
Hi
I try to figure out what is going wrong with the ServiceMix Bean
component when used with an asynchronous message exchange (send()).
There is a good chance to I do not understand how the message
exchange should work. This is what I tried:
- Bean SU 1 sends an In-Out ME to another Bean
On 10/16/07, Andreas Schaefer (2) [EMAIL PROTECTED] wrote:
Hi
I try to figure out what is going wrong with the ServiceMix Bean component
when used with an asynchronous message exchange (send()). There is a good
chance to I do not understand how the message exchange should work. This is
what
