On 9/7/07, Martin Novák <[EMAIL PROTECTED]> wrote:
> Hello, I'm having some difficulties running camel component from
> servicemix trunk.
>
> What am I trying to do is that: I want to call camel from within
> lightweight servicemix. I tried to do something like that: I create the
> DefaultSMClient, create a new inout exchange, and then send this
> exchange to the servicemix, and in servicemix, it will pass to some
> camel endpoint, do some routing, and pass to the other side of camel to
> call some other sm component, and get back with result. Is this possible
> scenario?
Yes, it should be. Thats exactly the kind of thing Camel is deal for;
if this doesn't work its a definite bug :)
> I cannot get this runnig. It's maybe a configuration problem,
> but I don't know. What have I seen in debugger, the CamelJbiEndpoint is
> created, but it is not registered anywhere inside the jbi container. I
> tried to use test cases for the camel compenent, and nothing again...
So the ServiceMix-Camel service unit should be creating JBI endpoints
that are registered on the NMR when you do...
from("jbi:...").to(....)
i.e. you consume in Camel from some JBI endpoint. It should then
activate that endpoint in JBI so you can send to it. We've got unit
tests for this; though we really could do with integration tests as
well.
FWIW there were some classloader issues with servicemix-camel which I
fixed last week; I wonder could you try retesting on trunk of camel
and servicemix to see if you're still having trouble? If you are, any
chance you could post some kinda example project/test case and we can
take a look trying to fix it?
BTW are you using the XML or Java approach to define the camel routing
rules? The classloader issues I fixed last week were to do with the
Java approach; the XML one seemed to already be working.
--
James
-------
http://macstrac.blogspot.com/
