Skip to content

Releases: camelot-framework/camelot

2.3.2

14 Sep 12:33
Compare
Choose a tag to compare

fixed timer invocation for all keys

2.3.1

14 Sep 12:32
Compare
Choose a tag to compare
  1. hz-context.xml renamed to repo-context
  2. fix in quartz scheduler

2.3

31 Aug 11:38
Compare
Choose a tag to compare
2.3
  1. Hazelcast v.3.5 with quorum support.
  2. Major improvements in aggregation and locking:
    • If unable to fetch state from the repo - message is resent to the same queue with a delay.
    • If unable to save state to the repo - original message is resent to the same queue with a delay.
    • Force unlock on the state is now called only if a consumer was not able to obtain the lock within a timeout.
    • Detection of dirty writes which can occur if a state was force-unlocked by a consumer thread while it was processed by another consumer. When a dirty write is detected the original message is resent with a delay.
    • Message is resent if the Camel context is already shutting down.
  3. Logging improvements

2.2.1

01 Jul 16:32
Compare
Choose a tag to compare
  • improved master Quartz initializer

2.2

19 Jun 13:31
Compare
Choose a tag to compare
2.2
  1. supported use of classnames for plugins with ids in camelot.xml
  2. fixed strange bug in logging that caused exception in Hazelcast aggregation repository
  3. added method in TestHelper to invoke specific aggregator timer method only
  4. throw exceptions out of TestHelper if invocation of timer method has failed
  5. fixed critical bug in camelot-test that caused the plugin states always to be saved in timer method regardless of the readOnly flag value in @OnTimer annotation
  6. improve front-end widgets engine:
    • throw $destroy event when widget is removed
    • do not reinitialize all other widget when any widget is removed
    • display plugins with dashboards on top of the widgets modal dialog

2.1.20

09 Jun 08:48
Compare
Choose a tag to compare

In this tiny release it is prohibited to build plugin dashboards using plugin id's specified in camelot.xml instead of java classNames of the plugins.

That is a subject for discussion but so far it the the proposed way of building front-end. At least because of the fact that front-end source code needs to be located under a directory called in accordance with the plugin java package. Plus widgets don't work with plugin id's. And the id's are just a string mappings whereas java classes are almost guaranteed to be unique.

2.1.19

08 Jun 17:16
Compare
Choose a tag to compare

Use https when importing bootstrap in wro.xml

2.1.18

05 Jun 14:04
Compare
Choose a tag to compare

Client notifications sender fix: Atmosphere broadcasters provider now supports topics with spaces & other non-urlencoded symbols.

2.1.17

18 May 17:11
Compare
Choose a tag to compare
  1. Allow to use plugin resources without aggregator/processor
  2. Allow to have an empty camlot.xml, i.e. with no <source> tags

2.1.16

12 May 09:24
Compare
Choose a tag to compare
  1. fix jackson marshalling for some cases
  2. extract bean declarations in camelot-processing-context for easier overriding