Skip to content

Changelog

Jump to bottom
joercampbell edited this page Nov 8, 2012 · 1 revision

What changed between various releases of Jrugged.

Table of Contents

Version 3.0.3 : 14 March 2012

  • Fixed issue #55: Use InitalizingBean extension rather than @Autowired
  • Fixed issue #54: Non-threadsafe usage of LatencyTracker in PerformanceMonitor
  • Fixed issue #53: Copyright year update
  • Fixed issue #50: Tread Safety in SampledQuantile
  • Issue #49: Updated Java doc information to clarify usage of Initializer
  • Issue #48: Autodiscover @CircuitBreaker Annotations

Version 3.0.0 : 19 September 2011

  • Fixed issue #35: Cleaned up and added Java Doc where it was missing
  • Fixed issue #37: Fixed an NPE in PerformanceMonitor
  • Fixed issue #38: NPE from DefaultFailureInterpreter (synchronization issue)
  • Enhancement issue #40: Allows a CircuitBreaker to start/initialize in a hard trip state.
  • Enhancement issue #41: Provide an exception mapper patter for the ConstantFlowRegulator
  • Fixed issue #42: Compilation error due to log4j dependency
  • Enhancement issue #43: The annotations available in the aspects package can now make use of the beans for PerformanceMonitors and CircuitBreakers allowing for a much cleaner implementation. The annotations are now much more useful and robust.
  • Enhancement issue #44: RolledUpStatus was improved to allow a more concise status reporting. The naming of the classes associated with the status have changed as well - to improve the readability and understandability of the code base.
  • Enhancement issue #45: Changed the pom's to include a more recent version of Spring (3.0.5)
  • Enhancement issue #46: Added a way in the spring integration to automatically 'discover' those classes with the annotations included in the aspects package to auto-publish their JMX information if there is a JMX server already registered in the spring config.
Many thanks to walter_eggert at comcast dot com, coby_young at comcast dot com, raghushankar_ramalingam at comcast dot com and michajlo_matijkiw at comcast dot com (Mishu) who contributed to this next great release of the JRugged Library.

Version 2.4.0 : 1 April 2011

  • Fixed issue #30: 2.3.0 didn't compile from source cleanly
  • Fixed issue #34: NPE in
  • Fixed issue #36: Method list had to have a comma in it to parse correctly
  • Added support for monitoring performance of HTTP calls to multiple hosts
  • Added a method for threading multiple service wrappers together in a chain

Version 2.0.0 : 16 March 2010

  • Added support for the Spring framework in the jrugged-spring subproject.
  • Refactored CircuitBreakers to use an external helper FailureInterpreter class to determine whether a failure should cause them to trip or not.
  • Simplified the !DefaultFailureInterpreter.
  • Renamed some classes in jrugged-aspects to more closely align with the naming of things in the jrugged-core library.
  • PerformanceMonitors now record their !MovingAverage updates inline rather than spawning a background thread to do periodic sampling.
  • Thorough Javadoc review and cleanup.

1.3.0 and older

  • We started maintaining this page with the 2.0.0 release, so if you would like details about previous releases please let us know via the jrugged-users list and we'll try to do the mining to fill this in....

Latest Stable Release:

jrugged-core-3.0.3.jar, jrugged-aspects-3.0.3.jar, jrugged-spring-3.0.3.jar, jrugged-httpclient-3.0.3.jar

Clone this wiki locally