-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: EVSIM-437 add message id in request metadata #70
feat: EVSIM-437 add message id in request metadata #70
Conversation
@@ -105,7 +105,7 @@ class OcppSoapServerTransport private constructor( | |||
msg.action?.lowercase() == action.lowercase() | |||
) { | |||
val message = ocppSoapParser.parseRequestFromSoap(msg.payload, clazz) | |||
val response = onAction(RequestMetadata(message.messageId), message.payload) | |||
val response = onAction(RequestMetadata(message.messageId, message.messageId), message.payload) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
c'est étrange ici on passe 2 fois le messageId ? Ca semble être une erreur dans l'implem actuelle qui passe le messageId en tant que chargingStationId ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
En effet c'est une erreur qu'on a dans l'implem actuelle, c'est corrigé
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good for me!
https://4sh-toolkit.atlassian.net/browse/EVSIM-437
Ajout du message id dans les request metadata afin qu'il soit directement accessible lors de l'implémentation des callbacks, qui ont la signature suivante par exemple :