Claus Ibsen created CAMEL-24391:
-----------------------------------
Summary: Add camel-as4 component for Peppol AS4 transport,
validation, and SMP lookup
Key: CAMEL-24391
URL: https://issues.apache.org/jira/browse/CAMEL-24391
Project: Camel
Issue Type: New Feature
Reporter: Claus Ibsen
Add a new camel-as4 component to provide Peppol AS4 transport support. Together
with the new camel-ubl data format (added in 4.23), this would give Camel a
complete Peppol e-Invoicing solution.
The component should cover three areas:
h3. 1. AS4 Transport
Implement the AS4 (ebMS 3.0) messaging profile used by the Peppol eDelivery
network. AS4 is the mandatory transport protocol for Peppol and is distinct
from AS2 (which serves traditional EDI/supply-chain). AS4 uses SOAP/WS-Security
for message exchange with signing, encryption, and receipt signals.
h3. 2. Peppol BIS Validation
Support for validating UBL documents against Peppol BIS (Business
Interoperability Specifications) rules, e.g. Peppol BIS Billing 3.0 for
invoices and credit notes. These are country-specific (CIUS) constraints on top
of UBL 2.1 that Peppol requires.
h3. 3. SMP/SML Lookup
Support for Peppol SMP (Service Metadata Publisher) and SML (Service Metadata
Locator) lookups to discover a recipient's access point URL and supported
document types. This is needed to route messages to the correct Peppol access
point.
h3. Together with camel-ubl
* camel-ubl: marshal/unmarshal UBL 2.1 documents (Invoice, CreditNote, Order,
etc.)
* camel-as4: transport (AS4), validation (Peppol BIS), and discovery (SMP/SML)
h3. Libraries to evaluate
[phase4|https://github.com/phax/phase4] by Philip Helger (same author as ph-ubl
used by camel-ubl), which provides a Peppol AS4 implementation and SMP client.
Peppol e-Invoicing is becoming increasingly important as more countries mandate
electronic invoicing, making this a strategic addition to Camel's B2B
integration capabilities.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
