CLD 1.5.0.S78 of edoras one is now available:
As a preparation for the complete clusterability of edoras one, all application level caches now use the Spring caching abstraction. The cache provider is
configurable in Spring and we use Ehcache as a default. In a clustered environment you are able to configure Ehcache to synchronize the caches or use a
Redis server as clustered cache.
We also integrated a first draft of the CMMN engine. Currently the engine is experimental and not production ready.
For end to end testing we now use Protractor to allow testing complex use cases and verify the behavior of edoras one from a user perspective.
Besides the things mentioned above, we have added various small improvements and many fixes.
edoras one team
- Use unified caching for all application level caches
- Support arbitrary REST endpoint call as an action in the menu of a work item
- Support custom properties for Case, PlanItems, CaseFileItems
- Integrate first draft of the CMMN engine
- Protractor integration
- In the vis-application-context.xml remove the property 'cacheExpireTime' from the bean definition of the com.edorasware.bpm.modeler.config.EditorConfiguration class
- In the vis-application-context.xml add a new bean declaration with the id 'paletteCache' and the class com.edorasware.palette.cache.PaletteCache. To this bean declaration add a constructor-arg element with name='cacheUtil' and ref='cacheUtil'
- In the vis-application-context.xml add a new bean declaration with the id 'visCache' and the class com.edorasware.cache.VisCache. To this bean declaration add a constructor-arg element with name='cacheUtil' and ref='cacheUtil'
- If you use edoras-one as an external dependency, add dependency on com.edorasware.one:edoras-cmmn:$edorasOneVersion to your project dependencies. Import '' in project's application context.
- If you use automatic application deployment at the start up, migrate applications to the new format (export an application from running project).