We are proud to anounce, that COPPER 4.0.0-alpha1 has just been released.

The most important new feature of this release is the Apache Cassandra support. Copper now comes with an adapter that connects to a Apache Cassandra NoSQL database. We love Cassandra because it offers high availability and really scales linear. Besides it is for free and open source. With Copper 4 you can run your persistent workflows on a Cassandra Cluster instead of a classic relational DBMS, e.g. MySQL or Postgres. See the cassandra getting started at cassandra-getting-started.txt on how to setup Copper using cassandra.

Besides the Cassandra support, we worked on some things to make usage of Copper easier, especially for new users. The new ClasspathWorkflowRepository is quite easy to use. No need for extra folders for the workflow java files, and no need for a JDK installation at runtime. Just pass the package names of those packages containing your Copper workflows - that’s all.

Furthermore we introduced some new EngineFactories which make it easier to create and start a Copper engine, see CassandraEngineFactory or RdbmsEngineFactory.

And last but no least, this release no more supports Java 6.

Our new COPPER ‘Getting started’ is now available. Check our docs.

We are proud to announce COPPER 3.2.1

This release mainly contains some fixes and enhancements in the monitoring:

Refactoring: Fixed many typos in copper-monitoring. Refactoring: Renamed Dashboard as Configuration in copper-monitoring-client. New feature: Preliminary version of the new Dashboard view. Bugfix: Issue #43: Copper Monitoring Workflows View - Total Count always 0. Bugfix: Issue #44: Copper Monitoring View - Workflow Repository multiple entry for workflow names. Bugfix: Issue #45: Copper Monitoring: High loading times for Dashboard and Resources views.

You can get it here: https://github.com/copper-engine/copper-engine/releases/tag/3.2.1

We are proud to announce COPPER 3.2.0

COPPER has been upgraded to ASM 5.0, so Java 8 is now supported!

You can get it here: https://github.com/copper-engine/copper-engine/releases/tag/3.2.0

We are proud to announce COPPER 3.1.0

• New feature: PersistentLockManager - a service to obtain/manager persistent locks, e.g. to functionally synchronize workflow instances.
• New feature: PersistentProcessorPool.suspendDequeue/resumeDequeue Suspends/resumes dequeuing of workflow instances from the storage.
• New feature: New utility org.copperengine.core.util.Backchannel, that offers functionality to signal a response from within a persistent workflow to its originator
• New feature: support for the H2 database
• New feature: added SimpleJmxExporter in copper-coreengine to ease the registering of JMX beans when COPPER runs without Spring
• Maven: copper-coreengine: moved dependency on C3P0 to copper-regtest. Removed *ConnectionCustomizer classes, because they broke the JDBC spec regarding autoCommit; also removed OracleConnectionTester as it can be substituted by setting ‘preferredTestQuery=”SELECT 1 FROM DUAL”’ in C3P0 datasource.
• Maven: copper-coreengine: removed unnecessary dependencies on aopalliance, findbugs-annotations and commons-codec, so the only remaining dependencies are on ASM and slf4j-api

You can get it here: https://github.com/copper-engine/copper-engine/releases/tag/3.1.0