TransportProfile AS4 refers to ESENS_AS4, but should it refer to PEPPOL_AS4_2_0
Closed this issue · 1 comments
WimMaerevoet-Octopus commented
Not sure where to make the issue ( vefa-peppol or oxalis-as4 )
We are busy implementing reporting requirements and use the InboundMetaData to collect the transportProfile.
In Oxalis-AS4 , the transport profile is hardcoded to TransportProfile.AS4, which corresponds to "bdxr-transport-ebms3-as4-v1p0"
I would expect "peppol-transport-as4-v2_0" - TransportProfile.PEPPOL_AS4_2_0
aaron-kumar commented
Fixed with a7efc70