Details
-
Bug
-
Status: Resolved
-
Resolution: Done
-
unspecified
-
None
-
None
-
Operating System: Linux
Platform: PC
-
3574
-
Normal
Description
1.In sfc-sb-rest, SbRestSfstEntryDataListener is not registered, so if the SF algorithm type changes, SFC can’t listen the change.
2.In sfc-provider, SfcProviderSfstEntryDataListener is not registered, so if the SF algorithm type changes, SFC can’t listen the change.
3.SfcProviderSfstEntryDataListener listens the creation, delete and update of sfsf, the internal procession is wrong, because if Algorithm type is created or deleted, then SbRestSfstEntryDataListener has processed it, SfcProviderSfstEntryDataListener does not need to process it again, and if Algorithm type is updated, it will cause the endless loop of SfcProviderSfstEntryDataListener.