At present, some questions are found in the implementation. Older SPI interfaces cannot inherit the org.apache.seata SPI interface because Seata's custom types are used in the interface. The current implementation of SPI is generic, requiring that the type of the parameter Class and the type of the returned instance must be the same. For specific questions, please refer to a PR I recently submitted[1].
[1]. https://github.com/apache/incubator-seata/pull/6403/files Warm regards, Ji Min yixia <[email protected]> 于2024年3月8日周五 21:59写道： > Most of the apache package compatibility migration has been completed and > needs to be reviewed. > > There are 10 folders in total. > > [image: image.png] > > Min Ji is responsible for the common, config, core, and discovery folders; > Te Wang responsible for the non-datasource modules, spring folder, and > saga folder in the rm folder; > funky-eyes is responsible for the datasource module, sqlparser folder, tm, > and integration folder in rm > > In addition, regarding SPI compatibility, we have reached the following > consensus. I am also responsible for this part of the work: > > 1) Our compatible scope is the SPI that users may use > 2) Most of the io.seata compatible interfaces should inherit the interface > of apache seata > 3) We will load all implementations of all apache.seata and io.seata > interfaces. The scenario io.seata with the same name covers the > implementation of apache.seata, and the log reminds >
