You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently SPSM config is async, but it doesn't work, as reported by a user in s-match/s-match-core#10 and by by @gbella :
The reason SPSM is not being executed while using the s-match-spsm.xml profile while it is executed when using the s-match-spsm-asymmetric.xml profile is that the former one is using asynchronous mode while the latter one is synchronous. However, the SPSM package does not have the "asyncTreeMatch" method implemented that the asyncMatchManager is trying to call. The result is that the asyncMatchManager falls back to a default tree matcher instead of SPSM. So the solution is to modify the s-match-spsm.xml to use synchronous mode instead (since we are not going to implement asynchronous SPSM). The way to do this is to replace in the XML the line:
<import resource="s-match.xml"/>
by
<import resource="s-match-synchronous.xml"/>
The text was updated successfully, but these errors were encountered:
Currently SPSM config is async, but it doesn't work, as reported by a user in s-match/s-match-core#10 and by by @gbella :
The reason SPSM is not being executed while using the
s-match-spsm.xml
profile while it is executed when using thes-match-spsm-asymmetric.xml
profile is that the former one is using asynchronous mode while the latter one is synchronous. However, the SPSM package does not have the "asyncTreeMatch" method implemented that the asyncMatchManager is trying to call. The result is that the asyncMatchManager falls back to a default tree matcher instead of SPSM. So the solution is to modify thes-match-spsm.xml
to use synchronous mode instead (since we are not going to implement asynchronous SPSM). The way to do this is to replace in the XML the line:by
The text was updated successfully, but these errors were encountered: