2.4.2

Fixed

• The issue, where there are no schema validations of command handler due to single war class loading EventFilter of Event Listener for handlers which then skips validation due to no match on the names with events.

2.4.1

Changed

• Removed duplicated test utilities from test-utils module
• Use test-utils project version of test utilities
• Use latest release versions of dependencies to fix OWASP vulnerabilities

2.3.3

##Changed
Replaced the JsonObjectObfuscator with the version from utilities that is based on javax.json

2.2.2

Changed

• Utilities library upgraded to 1.8.1 and file service to 1.11.1 to pick up JSON logging fix

2.2.1

Changed

• Converted to release to bintray
• Converted example context to run as a single war by default

Fixed

• Class conflicts between generated clients in a single war

2.2.0

Changed

• Use maven-framework-parent-pom 1.6.1, which simply changes the wildfly-maven-plugin to 1.2.0.Alpha6 and stops adding it to every build
• example-it: move the wildfly operations to the pre/post-integration-test phases (where they belong)
• Switch to bintray for release processes
• Cleaned up some unnecessary version overrides

2.1.0

Added

• New test matcher for checking schema properties

Fixed

• Aggregate snapshot repository did not use aggregate class when retrieving snapshots, so services that use multiple aggregate classes
  on the same stream could get class cast exceptions

2.0.0

Changed

• Refactor all framework components that are not internal so that they are provided as interfaces
  via new Framework API modules
• Rework interceptor chain so that it is specific to a service component, by allowing each component
  to provide an interceptor chain definition rather than using annotation scanning
• Upgrade to use framework parent POM 1.5.0
• Upgrade to use common BOM 1.16.0
• Interceptor chain now adds the component name to the context so it can be used by the access control interceptor or anything else that needs it
• Logging dependencies tidied up - all logging implementations excluded from dependencies and tests use new test utils modules for logging
• Generated class names made more unique, including adding the base URI in class name for generated JMS listeners. Any project that overrides the generated
  class will need to change the class name of their override to match
• Improved logging for annotation scanning
• Add component to audit interceptor so that audit messages can distinguish between components even
  when they are deployed in a single WAR.

Removed

• Support for default sender destinations removed; senders now always require messaging clients to
  be provided, typically by generating one from the destination RAML.
• Access control Provider annotation and annotation scanning; this functionality has moved to the access control library
• Precondition class marked as deprecated - will be removed in 3.0.0 unless a different use case is found for it

Fixed

• Test cases for random ZonedDateTime generators and added logging to show more info when they fail
• Javadoc errors
• Aggregate snapshot service was pulling in Liquibase due to an incorrect dependency scope
• Remove audit from event listener and event processor

Added

• Script for building dependencies locally
• Support for generating and discovering direct adapters, if a message destination exists locally
  a service component in the same application

2.0.0-rc8

Fixed

• Remove audit from event listener and event processor

2.0.0-rc7

Changed

• Message client generated class name no longer enforces base URI pattern