Skip to content

Releases: camelot-framework/camelot

2.4.8-20151118

18 Nov 16:16
Compare
Choose a tag to compare
2.4.8-20151118 Pre-release
Pre-release
  1. fix discarding all states and queues in camelot-test

2.4.7

17 Nov 19:08
Compare
Choose a tag to compare
  1. fixed quartz scheduler locking
  2. fix for NoSuchElementException in mongo adapter
  3. fixed bug in camelot-test
  4. fixed circular dependency
  5. remove exceptions logging in mongo adapter when unable to connect
  6. refact quartz initializers

2.4.6

15 Nov 00:24
Compare
Choose a tag to compare
  • Bunch of fixes
  • Java 8 migration + latest Spring&Camel dependencies
  • MongoDB extension

2.4.5

15 Nov 00:25
Compare
Choose a tag to compare
2.4.5 Pre-release
Pre-release

Technical release. Should not be used at all.

2.4.4

29 Oct 16:26
Compare
Choose a tag to compare
  • API changes: some spring beans renamed
  • extracted camelot-properties-context.xml
  • hazelcast TargetDisconnectedException and OperationTimeoutException and now caught
  • resent messages ids are now logged on debug level

2.4.3

12 Oct 12:24
Compare
Choose a tag to compare
  • Fixed uri builders to make only certain routes with seda
  • Fixed webfront context

2.4.2

06 Oct 10:47
Compare
Choose a tag to compare

No changes, was released because of technical difficulties.

2.4.1

05 Oct 17:59
Compare
Choose a tag to compare
  1. Critical fix in hazelcast storage
  2. Critical fix for atmosphere websockets when using camelot-front

2.4.0

05 Oct 17:57
Compare
Choose a tag to compare
  1. Modules repackaging, contexts renaming
  2. Activemq and Hazelcast are not used now by default
  3. Extensions support with Activemq, Kafka and Hazelcast extensions provided

2.3.3

16 Sep 16:21
Compare
Choose a tag to compare
  1. Refactored spring contexts to simplify overriding some beans if needed. Now all classpath files called camelot-extensions.xml will be added to the application context, overriding anything that is used by default.
  2. Default properties file renamed to camelot-default.properties to avoid conflicts with camelot.properties provided by the user. The latter is loaded after the default to ensure properties overriding.
  3. camelot-core.jar file is now runnable. When invoked via java -jar command it will search for camelot.xml across the whole classpath and launch a camelot instance with the specified plugins. No front-end will be initialized.
  4. camelot-front module is added. When camelot-front.war is launched in a servlet container it will instantiate a web-front camelot engine, but skip the messages processing module.