Apache ServiceComb Pack is an eventually data consistency solution for micro-service applications. ServiceComb Pack currently provides TCC and Saga distributed transaction co-ordination solutions by using Alpha as a transaction coordinator and Omega as an transaction agent .
Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
Omega AutoConfiguration
OmegaSagaSpringConfig using omega.spec.names=saga
OmegaTccSpringConfig using omega.spec.names=tcc
TransactionAspectConfig class of the omega-spring-tx module uses ConditionalOnExpression to initialize beans
Legacy Issue
[Duplicate Code]Create class EclipseLinkJpaConfiguration in test case to avoid dependency on class EclipseLinkJpaConfiguration in alpha-persistence-jpa module
[Duplicate Code]Because of the metrics API, each Spec module contains same classes as follows
Jira issue https://issues.apache.org/jira/browse/SCB-2425
Alpha Module
Alpha Using Spring SPI
Alpha Configuration
Omega Modules
Omega AutoConfiguration
Legacy Issue
[Duplicate Code]Create class EclipseLinkJpaConfiguration in test case to avoid dependency on class EclipseLinkJpaConfiguration in alpha-persistence-jpa module
[Duplicate Code]Because of the metrics API, each Spec module contains same classes as follows
saga-db saga-akka and tcc-db cannot be used together
Refactor Redis and Rabbit channel configuration in saga-akka module