You are correct, I have just added the folllowing section to
http://mule.mulesource.org/display/MULE2INTRO/Migrating+Mule+2.0+to+2.1explaining this.
Retry Policies (ex-Reconnection Strategies)
-------------------------------------------
Due to some fundamental issues with the previous implementation of
Reconnection Strategies, these have now been redesigned and renamed to
"Retry Policies". The API for implementing retry policies is available
in org.mule.api.retry and related classes in org.mule.retry
Mule Enterprise includes common retry policies which can be configured
in your XML (e.g., <retry:simple-policy count="5" frequency="1000"/>)
but Mule Community users will need to implement their own based on
org.mule.retry.policies.AbstractPolicyTemplate
Travis
On Thu, 2008-10-09 at 09:29 -0700, NiHeitz wrote:
> Just attempted to upgrade to new Mule 2.1.0. It seems that there is no
> longer a SimpleRetryConnection class for failed jms connections using
> ActiveMQ. This was present and worked in Mule 2.0.3. I read the upgrade
> path document, and it makes no mention of the removal of this strategy...is
> there a replacement approach?
>
> My connections no longer recover, and my configuration breaks. Looks like
> there is a new RetryPolicy framework, but no concrete Implementation classes
> for actually attempting a retry that has iterations and delays. Work in
> progress? Not available for community edition?
>
> Any help?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
