Skip to content
Commits on Feb 3, 2016
  1. @garyrussell

    Add Code of Conduct

    garyrussell committed
Commits on Nov 11, 2014
  1. @dsyer

    Add javadocs report

    dsyer committed
  2. @dsyer

    Add wagon provider for ssh

    dsyer committed
Commits on Sep 30, 2014
  1. @dsyer
  2. @dsyer
Commits on Sep 19, 2014
  1. @dsyer
  2. @dsyer

    Remove unused local variable

    dsyer committed
  3. @dsyer
  4. @dsyer

    Spelling mistake

    dsyer committed
Commits on Aug 28, 2014
  1. @dsyer
  2. @dsyer
  3. @dsyer

    Bump release plugin

    dsyer committed
Commits on Aug 22, 2014
  1. @dsyer

    Fixes gh-12: correct Javadocs

    dsyer committed
    The method signature for RetryCallback was changed in 1.1 but the
    Javadocs in RetryTemplate still reflected the old behaviour.
  2. @artembilan @dsyer

    Fix `@EnableRetry` do not proxy all beans

    artembilan committed with dsyer
    Fixes #13
    
    Previously the `@EnableRetry` caused to proxy **all** beans in the context, because
    of `IntroductionAdvisor` nature in the `AopUtils` logic and simple `ClassFilter.TRUE`
    in that case. In the end it just skipped `MethodMatcher` and applied `ProxyFactory` for any bean.
    
    Since we can't avoid `IntroductionAdvisor` because of `getInterfaces()` introduction,
    provide a new internal `AnnotationClassOrMethodFilter` to apply both class and method level annotation filter at once.
    
    Polishing for the `AnnotationAwareRetryOperationsInterceptor` to skip non-`@Retryable` methods and just call `invocation.proceed()`
    
    Fixes gh-13, fixes gh-14
Commits on May 15, 2014
  1. @dsyer

    Use Spring BOM for dependencies

    dsyer committed
Commits on May 13, 2014
  1. @dsyer

    Move to next SNAPSHOT

    dsyer committed
  2. @dsyer

    Update to 1.1.0.RELEASE

    dsyer committed
Commits on May 12, 2014
  1. @dsyer

    Update to 1.1.0.RC3

    dsyer committed
  2. @dsyer

    Add `RetryInterceptorBuilder` support

    Artem Bilan committed with dsyer
    * Add `RetryInterceptorBuilder` and its tests
    * Add usage from `AnnotationAwareRetryOperationsInterceptor`
    * Add `Retryable#interceptor()` option to use full Retry Interceptor from `BeanFactory`
    * Fix `RetryConfiguration` `beanFactory` propagation
    
    Fixes gh-11
  3. @dsyer

    Code Cleanup

    Artem Bilan committed with dsyer
    * Deprecate `ObjectWaitSleeper` and replace it with `ThreadWaitSleeper`
    * Improve `SimpleMethodInvoker`
    * Use `if (logger.isDebugEnabled())` for better performance
    
    The `RetryTemplate` continues to invoke `canRetry(retryPolicy, context)` with retry loop, because some end application may rely on that logic.
    Although it looks like overhead to call `canRetry()` twice a retry: it might be heavy operation, e.g. check the state of external system
    
    Fixes gh-10
Commits on May 7, 2014
  1. @dsyer
  2. @dsyer

    Tidy up @Retryable

    dsyer committed
    * Add some docs to backoff()
    * Remove unnecessary @Import
Commits on May 3, 2014
  1. @dsyer
  2. @dsyer
  3. @dsyer

    Switch back to Java 1.6

    dsyer committed
Commits on Apr 25, 2014
  1. @dsyer
  2. @dsyer
  3. @dsyer

    Fix pom for release

    dsyer committed
Commits on Apr 24, 2014
  1. @dsyer

    Add Retryable interface for proxies advising @Retryable beans

    dsyer committed
    This is purely a marker interface, but might be useful for other tools
    looking to apply retry advice (they should usually not bother if the
    bean already implements Retryable)
  2. @dsyer

    Parameterize exception type in RetryCallback

    dsyer committed
    So RetryCallback<T, E extends Throwable> and the E parameter appears
    in RetryOperations too, making it possible to call it with an unchecked
    exception type in the parameter and not catch exceptions.
    
    Users should beware: it's just syntactic sugar, and the actual runtime
    type of the exception is never checked at runtime. So, for instance,
    declaring a RetryCallback<Object,IllegalArgumentException> doesn't
    mean that other Exceptions won't be retried, just that you won't be
    able to explicitly throw them if they are checked.
    
    A project using Spring Batch 2.2 was used to test that this works
    with user code that uses a library compiled agains Spring Retry 1.0.
    
    Fixes gh-6
  3. @dsyer

    Add support for @Recover

    dsyer committed
Commits on Apr 23, 2014
  1. @dsyer

    Remove OSGi template.mf

    dsyer committed
  2. @dsyer

    Add README from Spring Batch docs

    dsyer committed
Commits on Apr 22, 2014
  1. @dsyer

    Change method signatures to Throwable (from Exception)

    dsyer committed
    This allows use of spring-retry with naughty libraries that use Error
    conditions to signal retryable exceptions. Users can still declare their
    RetryCallback as "throws Exception" if they want to be conservative.
    
    Also added throwLastExceptionOnExhausted to RetryTemplate to throw
    the last exception instead of the ExhaustedRetryException.
  2. @dsyer

    Fix copyrights

    dsyer committed
Something went wrong with that request. Please try again.