what if I am not using CamelTestSupport?
Stephen Gargan wrote:
>
> If you're using CamelTestSupport you can do the following...
>
> @Override
> protected Context createJndiContext() throws Exception {
> Context jndi = super.createJndiContext();
> jndi.bind("myRetryBean", "somebean");
> System.err.println(jndi.lookup("myRetryBean"));
> return jndi;
> }
>
> On Wed, Feb 10, 2010 at 10:23 AM, mcrive <mcr...@optasportsdata.com>
> wrote:
>>
>> Hi,
>> I have built current trunk
>> and tried to use retryUntil on my context (see
>> https://issues.apache.org/activemq/browse/CAMEL-2360)
>>
>> Now something happens!
>> An exception :) which is a good thing it means the background works!
>>
>> org.springframework.jms.listener.DefaultMessageListenerContainer -
>> Execution of JMS message listener failed
>> org.apache.camel.language.bean.RuntimeBeanExpressionException: Failed to
>> invoke method: null on myRetryBean due to:
>> org.apache.camel.NoSuchBeanException: No bean could be found in the
>> registry
>> for: myRetryBean
>>
>>
>> how should I add the bean to the registry, at the moment I am doing this:
>> JndiRegistry jndi = new JndiRegistry(new JndiContext());
>> jndi.bind("myRetryBean", new RetryBean());
>>
>> looking into the unit tests I can't find any sample...
>>
>>
>>
>>
>>
>> Claus Ibsen-2 wrote:
>>>
>>> On Thu, Feb 4, 2010 at 9:34 AM, mcrive <mcr...@optasportsdata.com>
>>> wrote:
>>>>
>>>> is building current trunk another option?
>>>>
>>>
>>> Yeah of course you are welcome to build and try the trunk
>>> http://camel.apache.org/building.html
>>>
>>>>
>>>> Claus Ibsen-2 wrote:
>>>>>
>>>>> On Wed, Feb 3, 2010 at 2:40 PM, mcrive <mcr...@optasportsdata.com>
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> mcrive wrote:
>>>>>>>
>>>>>>> I've tried both things you suggested but it is still not working,
>>>>>>> the
>>>>>>> retry happens in default manner.
>>>>>>>
>>>>>>> I've opened a ticket in JIRA:
>>>>>>> https://issues.apache.org/activemq/browse/CAMEL-2360
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> were you able to replicate the issue I am experiencing? I've attached
>>>>>> a
>>>>>> sample to the ticket.
>>>>>>
>>>>>
>>>>> I did some fixes which will be in 2.2. So can you try again when Camel
>>>>> 2.2.0 has been released.
>>>>>
>>>>>
>>>>>> --
>>>>>> View this message in context:
>>>>>> http://old.nabble.com/recipientList-retryUntil-not-working--tp27145846p27436399.html
>>>>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> Apache Camel Committer
>>>>>
>>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>> Open Source Integration: http://fusesource.com
>>>>> Blog: http://davsclaus.blogspot.com/
>>>>> Twitter: http://twitter.com/davsclaus
>>>>>
>>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://old.nabble.com/recipientList-retryUntil-not-working--tp27145846p27449274.html
>>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> Apache Camel Committer
>>>
>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>> Open Source Integration: http://fusesource.com
>>> Blog: http://davsclaus.blogspot.com/
>>> Twitter: http://twitter.com/davsclaus
>>>
>>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/recipientList-retryUntil-not-working--tp27145846p27535743.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context:
http://old.nabble.com/recipientList-retryUntil-not-working--tp27145846p27543553.html
Sent from the Camel - Users mailing list archive at Nabble.com.
