Releases: camelot-framework/camelot
Releases · camelot-framework/camelot
2.4.8-20151118
- fix discarding all states and queues in camelot-test
2.4.7
- fixed quartz scheduler locking
- fix for NoSuchElementException in mongo adapter
- fixed bug in camelot-test
- fixed circular dependency
- remove exceptions logging in mongo adapter when unable to connect
- refact quartz initializers
2.4.6
- Bunch of fixes
- Java 8 migration + latest Spring&Camel dependencies
- MongoDB extension
2.4.5
Technical release. Should not be used at all.
2.4.4
- 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
- Fixed uri builders to make only certain routes with seda
- Fixed webfront context
2.4.2
No changes, was released because of technical difficulties.
2.4.1
- Critical fix in hazelcast storage
- Critical fix for atmosphere websockets when using camelot-front
2.4.0
- Modules repackaging, contexts renaming
- Activemq and Hazelcast are not used now by default
- Extensions support with Activemq, Kafka and Hazelcast extensions provided
2.3.3
- 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. - Default properties file renamed to
camelot-default.properties
to avoid conflicts withcamelot.properties
provided by the user. The latter is loaded after the default to ensure properties overriding. - camelot-core.jar file is now runnable. When invoked via
java -jar
command it will search forcamelot.xml
across the whole classpath and launch a camelot instance with the specified plugins. No front-end will be initialized. - 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.