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
I am opening this issue with the intent to suggest a little improvement.
This morning I did some inbound tests. The sender produced an AS4 SOAP Envelope not suitable with OpenPEPPOL 4 corner scenario.
He basically omitted UserMessage / MessageProperties field. If I am right, this field is defined as optional in OASIS standard, but it is mandatory in PEPPOL scenario because the receiver must verify its values (they must match with the ones defined in SBDH), referring to this.
Oxalis threw a NullPointerException on no.difi.oxalis.as4.inbound.As4InboundHandler:446:
I thought it would be useful to share this with you.
Maybe this case could be handled throwing a checked Exception or something similar just to avoid NullPointerException.
The issue has been solved by fixing the sender's SOAP Envelope. I opened this on GitHub just to share the case.
Hi all,
I am opening this issue with the intent to suggest a little improvement.
This morning I did some inbound tests. The sender produced an AS4 SOAP Envelope not suitable with OpenPEPPOL 4 corner scenario.
He basically omitted UserMessage / MessageProperties field. If I am right, this field is defined as optional in OASIS standard, but it is mandatory in PEPPOL scenario because the receiver must verify its values (they must match with the ones defined in SBDH), referring to this.
Oxalis threw a NullPointerException on no.difi.oxalis.as4.inbound.As4InboundHandler:446:
I thought it would be useful to share this with you.
Maybe this case could be handled throwing a checked Exception or something similar just to avoid
NullPointerException
.The issue has been solved by fixing the sender's SOAP Envelope. I opened this on GitHub just to share the case.
Oxalis AS4 plugin version: 4.1.9 (latest release available).
Have a nice day and stay safe!
Manuel
The text was updated successfully, but these errors were encountered: