Skip to content
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.

Sign up for GitHub

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

Jump to bottom

TransportProfile AS4 refers to ESENS_AS4, but should it refer to PEPPOL_AS4_2_0 #53

Closed
WimMaerevoet-Octopus opened this issue Nov 10, 2023 · 1 comment
Closed

TransportProfile AS4 refers to ESENS_AS4, but should it refer to PEPPOL_AS4_2_0 #53

WimMaerevoet-Octopus opened this issue Nov 10, 2023 · 1 comment

Comments

@WimMaerevoet-Octopus
Copy link

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
Copy link
Member

Fixed with a7efc70

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aaron-kumar @WimMaerevoet-Octopus