This is still a bugfix release. We've to modify the header of all JMS messages to be compatible with the JMS Spec (and especially Bea Weblogic 12c). So all all JMS-Messages still in queues or TracEE-producers and -consumers prior 1.2.0 are incompatible. Please check your environment and queues or test the upgrade on your side very well.

Fixed issues

• #168 Illegal Message.setObjectProperty() call on JMS binding with PR #176

Thanks to @eruiz to find the issue.

We've released a new bugfix release of TracEE. Following changes are included:

• #136, #137: springmvc binding: Write the TracEE-Header to response right after receiving the request and try to replace it later on. This is a small workaround for large or already commited response bodies where TracEE isn't able to write the TPIC header.
• #138: documentation update: Instead of LATEST version we point to a ${tracee.version}-variable because LATEST isn't a valid version specification since Apache Maven 3.0
• #140, #142: spring-jms: If no invocationId could be read from the JMS message, TracEE should generate a new one. (Thanks to @Hippoom for the contribution)

This is a bugfix releace for some integration issues:

Bugfixes

• #134 (PR: #135) Using tracee-jaxrs2 with CDI (WELD) a proxy generation exception is raised due some final methods. The final keyword has been removed in the TraceeClientFilter and TraceeContainerFilter (Thanks to Flosus)
• #131 (PR: #132) Spring-MVC module pulls Logback into the classpath. That's bad if other log implementation is used.

Other fixes

• #133: Some test refactoring of the BackendBase and the default Slf4J-Backend test.
• #126: Small test to demonstrate how to use the module tracee-springhttpclient with old fashioned XML configuration of the spring context.

The new version of TracEE enables you to use Springs @Async-Annotation. The TPIC is propagated to the asynchronous execution thread and cleared after execution. Due such change we've to raise the required Spring-Framework version to 3.2. If you don't use the BeanPostProcessors, you should use Spring Framework 3.1 (or maybe older) as well.

Issue fixed:
#122 - MDC inheritance should be handled by tracee
with: #123 - Solve #122: Add bean post processors to copy and set TPIC to async process
and: #124 - Update required Spring Version to 3.2.x

Other stuff:

• #125 - Update min maven version to the latest with java6 support

This is the first bugfix release since our first major version tracee-1.0.0.

We consider this bugfix to be backward compatible. You can directly upgrade from tracee-1.0.0 to tracee-1.0.1.

Changes in tracee-1.0.1

• #120: SpringMVC: Missing TPIC in response header if mvc-interceptor chain is interrupted

We're quite happy to announce TracEE 1.0.0

No changes were made to the production code since the last release candidate. But since the last release we treat compiler warnings as errors, in order to keep our code clean as possible.

We've eliminated a small issue in the CXF module: a comparison of a boolean variable has been done by equals signs instead of using the equals-Method. This could be a small issue if someone init the values in CXF with new Boolean(true) for example. I think noone does such stupid things so it is just a fix for FindBugs/Coverity ;-)

The reason for the new release candidate is a small new feature: We've created a new BOM-module to support the dependency management for the tracee modules. See into the (BOM-Module for usage instructions)[https://github.com/tracee/tracee/blob/master/bom/README.md].
In addition we've added more test cases and slight refactorings.

We're exited to publish the first release candidate of TracEE.

Following bugfixes and improvements has been included:

• #105: Manifest of the Spring WS module includes OSGi entries (Bug)
• #106, #107: The CXF module is working without SOAP extention on the classpath (Bug)
• #108: Classes of the testhelper module moved in an own package (Refactoring)
• #109, #112: More test cases and small refactorings (Refactoring)
• #111: If no own TraceeBackendProvider could be located with the SPI file the SLF4J default backend is added to the cache as well. This implementation could be faster in some circumstances (Improvement)

We're exited to announce a new version of the tracee. This will be the last version with major changes before we enter the release candidate cycle for tracee 1.0. Here come the changes since 0.11:

• #104 Drop Tracee-Backend infrastructor in favor of SLF4J. The most important change: We removed our backend infrastructure and committed our backend to SLF4J. So you will no longer to add a dependency for a logging backend, adding tracee-core (even transitively) is sufficient. You may still provide your own backend implementation via the known SPI mechanism, but slf4j will be the default if no SPI implementation is available on the classpath.
• #103 Parse all headers of SOAP message instead of only the first one__ - This change merges the propagated context map from multiple soap headers if provided. This allows interceptors to add context information without understanding the structure of the encoded TPIC body.
• Upgraded the version of build-plugins and test-dependencies