hange of CAMEL-1777[1].
> So I created a JIRA[2] for it and will did a quick fix for it.
>
> [1]http://issues.apache.org/activemq/browse/CAMEL-1777
> [2]http://issues.apache.org/activemq/browse/CAMEL-2060
>
> Willem
>
> sasidharm wrote:
>> Here is a t
Here is a test that illustrates the issue:
import javax.naming.Context;
import junit.framework.Assert;
import org.apache.camel.ContextTestSupport;
import org.apache.camel.builder.RouteBuilder;
import org.apache.camel.util.jndi.JndiContext;
public class CamelBeanEndpointTest extends ContextTestSu
I am trying to upgrade to Camel 2.0 and running into a weird issue. Say i
have the following route:
Here i am not specifying any method name explicitly for bean1 and I am
depending on Camel's bean binding.
The first time a message is pulled from jms:jms/queue, the cor
