Also, theres some test code here
http://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/org/apache/camel/processor/SplitterMethodCallTest.java
http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/java/org/apache/camel/spring/processor/SpringSplitterMethodCallT
2009/1/30 mta38 :
>
> Hi all,
> I want to test splitter processor and i have implemented my own Splitter
> expression in java code:
>
> Public class MySplitter extends Expression{
>
>public Object evaluate(Exchange arg0) {
>//my code
>}
> }
>
> class="com.francetele
Hi all,
I want to test splitter processor and i have implemented my own Splitter
expression in java code:
Public class MySplitter extends Expression{
public Object evaluate(Exchange arg0) {
//my code
}
}
FTR, it does not really cache consumers. Caching consumers is
problematic as it can lead to messages being kinda lost if they are
unconsumed and the consumer is not closed.
On Fri, Jan 30, 2009 at 05:53, chrajanirao wrote:
>
> I just realized that we need to use
> "org.springframework.jms.connec
2009/1/30 chrajanirao :
>
> I just realized that we need to use
> "org.springframework.jms.connection.CachingConnectionFactory". As of spring
> 2.5.6, this supports caching of connection/sessions/consumers/producers and
> is strongly recommended to use with JmsTransactionManager!
Lets do it :)
--
I've put together a crude mechanism for starting/stopping routes by the name
of their endpoint. I do agree however that adding/deleting is probably a
nicer way of dealing with state.
I had to patch two classes in the Camel library.
The EventdrivenConsumerRoute has to retain its consumer so that
