During development and integration of JDBC persistence store into the EAP 7.1, the custom implementation of SQLProvider interface [1] was developed for EAP use case. The reason was that EAP 7.1 used Artemis 1.x which was at that time maintenance branch and thus development of new features was focused on 2.x branch.
Since EAP 7.2 is going to be based on Artemis 2.x it should drop it's SQLProvider implementation and use the Artemis' one. If there are some differences in set of supported database vendors, these "ahead changes" should be contributed to Artemis code base to avoid duplication of code.
- is cloned by
-
WFLY-10580 WildFly should use Artemis' SQLProvider implementation
- Closed
- relates to
-
WFLY-10320 Upgrade artemis from 1.5.x to 2.x.x
- Closed
- is blocked by
-
ARTEMIS-1590 Loading...