- FIXED
- #39 解决Policy定位的扩展点如果不存在则抛出NullPointerException
-
FIXED
-
Feature
- #37 除了
Partner/Pattern
的静态的扩展点路由机制外,提供了动态路由机制:Policy
,供使用者扩展 - #35 提供绕过
BaseDomainAbility
而直接路由扩展点的机制,在业务属性不明显的场景下使用 - #32 框架提供默认的步骤编排能力,使用者不必从头编写
Ability
来编排步骤 - 增加了一个使用
DDDplus
来搭建low-code
平台的例子工程:https://github.com/dddplus/easyapp- 其中的Trigger机制依靠扩展点和Plugin的动态加载实现
- #37 除了
-
FIXED
- #20 Plugin reloading, Spring unable to get the Partner bean
- #28 ArchitectureEnforcer的接口规范 bug,需要把注解排除在外
- dddplus/dddplus#4 在Spring Boot集成时,无法触发
IStartupListener
-
Improvement
-
Feature
-
Test
- #26 Stress test for plugin jar reloading passed
-
FIXED
- NPE when Plugin load without using Spring
-
Improvement
- Add Specification & Notification Pattern to DDDplus for explicit business rules expression
-
Improvement
- Integrated with CodeQL
- Being renamed to DDDplus
- Container.java and Plugin.java refactored: explicit over implicit
- Plugin jar reloading will not allow concurrency
-
Test
- NamedThreadFactory test case bug fixed