Yes.
Also, ServiceMix EIP had xpath splitter, which I didn't see in Camel?
James.Strachan wrote:
>
> ...
> We should probably
> integrate Camel into ServiceMix as the preferred EIP solution and
> consider deprecating (or at least merging) the ServiceMix EIP
> functionality.
>
> --
> James
>
What is the relation of Camel to ServiceMix-EIP?
Is one somehow the historical ancestor of the other?
Or are they intended to be equivalent functionality, but in different
settings?
--
View this message in context:
http://www.nabble.com/-camel--tf3796253s2354.html#a10737590
Sent from the Active
support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:75)
at
org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:65)
...
James.Strachan wrote:
>
> On 5/3/07, dr.jeff <[EMAIL PROTECTED]> wrote:
>>
>>
>&
http://activemq.apache.org/camel/schema/camel-1.0.xsd";>
This looks good, but how do I use it?
I've tried things like:
and and and https://svn.apache.org/repos/asf/activemq/camel/trunk/camel-spring/src/test/resources/org/apache/camel/spring/endpointReference.xml
>
> whe
5/2/07, dr.jeff <[EMAIL PROTECTED]> wrote:
>>
>> Good stuff.
>> It might be useful to be able to refer from the camelContext out into the
>> wider Spring beans context (I would find it useful):
>>
>>
>>
>>
>>
>>
>>
>&
Good stuff.
It might be useful to be able to refer from the camelContext out into the
wider Spring beans context (I would find it useful):
...
...
James.Strachan wrote:
>
> Yeah, we could definitely have some kinda mechanism like that. Maybe
>
>
>
>
>
>
It would help to avoid these kind of errors if there was some mechanism in
place to refer to URIs by reference, somewhat in the way that Spring refs
work. If I have:
then I can do:
...
because I have more than one flow using transformers.
My suggestion is
My xml looks like this:
http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
http://www.springframework.org/schema/beans ./spring-beans-2.0.xsd
http://activemq.apache.org/camel/schema/camel-1.0.xsd ./camel-1.0.xsd
Yes. That works now. Thanks.
James.Strachan wrote:
>
> On 4/30/07, dr.jeff <[EMAIL PROTECTED]> wrote:
>>
>> If I use the example at:
>>
>> http://svn.apache.org/repos/asf/activemq/camel/trunk/camel-spring/src/te
If I use the example at:
http://svn.apache.org/repos/asf/activemq/camel/trunk/camel-spring/src/test/resources/org/apache/camel/spring/routingUsingCamelContextFactoryWithNamespacesTest.xml
then I get this exception
Exception in thread "main"
org.springframework.beans.factory.xml.XmlBeanDefinitio
I have tried and completely failed to use the camel spring container.
I see where it can do two things:
1) create a context which instantiates RouteBuilders in a given package:
I can't even guess what the need for that is, unless it's just a shortcut
for declaring those RouteBuilders
I know how to make custom splitters in the Camel DSL way by extending
org.apache.camel.builder.ValueBuilder with a new operation that returns my
own Expression, that splits the message in the way I need it to. (And I
think that's the correct general approach to take, but correct me.)
But I just do
ways.
Hope that's clear???
James.Strachan wrote:
>
> On 4/20/07, dr.jeff <[EMAIL PROTECTED]> wrote:
>> I was attracted to Camel by the existance of the MINA component, but I
>> now
>> see that it has some deficiencies.
>
> I hope we can work on th
I was attracted to Camel by the existance of the MINA component, but I now
see that it has some deficiencies.
Very generally there can be 4 kinds of MINA endpoints:
1) acceptors ("server sockets", that accept connections) that initiatiate
request/responses,
2) acceptors that wait for requests (eg,
What is the intended usage of interceptors?
Do I get the get the message from exchange.getIn() and, say, modify its
body?
Or should I somehow be putting the modifications into the exchange.getOut()
message?
--
View this message in context:
http://www.nabble.com/-camel--How-to-user-InterceptorPro
I have a SOAP client component that I am hooking up like this:
from("queue:requests").to("soap.client:http://a.b.c:80/soap-service";);
from("soap.client:http://a.b.c:80/soap-service";).to("queue.responses");
(This is part of a bigger flow that is pulling in messages
16 matches
Mail list logo