holodeck-b2b/file-backend

Holodeck B2B extension that implements a file based back-end integration

file-backend's Issues

Outdated hb2b version in pom.xml

The HB2B version in the pom.xml should be updated to 5.3.1:

<holodeckb2b.version>5.1.0</holodeckb2b.version>

Delivery operation does not use HB2B home as base for relative path parameter

When the deliveryDir parameter of the delivery operation is a relative path it is not evaluated against the Holodeck B2B home directory but the directory where Holodeck B2B is installed.

Use a temporary extension when writing meta-data files

Currently the meta-data file uses the xml extension when it is being written to disk. This may cause the receiving back-end application to start reading it before the delivery operation has finished. It would therefore be better to use a temporary extension when writing the file to disk and rename it as last step.

Change default removal of payloads after submission

In the file based back end integrator the current default is that after submission, files are not removed unless the back end system instructs Holodeck B2B to do so.
This can cause disk space to run out if the back end system does not do this (or not properly).
Sent payloads must then be removed manually or using a script.
Solution: Switch to default file removal after submission.

Requested delivery format ignored

Even when specifying the delivery format as "mmd" or "single_xml" the "ebms" format is used.

Make default removal of submitted payloads configurable

After implementing #2 submitted payloads files are removed by default. If these files should be kept, for example for archiving or sending to another partner, the back-end needs to indicate this in the MMD. This behaviour therefore causes backwards incompatibility and requires a change in the back-end application. It would therefore be better if the default removal of submitted payloads is configurable so it can be disabled in cases where payload files should be kept.

It would be nice if inbound mmd files showed the pmode even if it was found by matching.

Currently, if a inbound message has an agreement then the MMD has:

<AgreementRef>http://agreements.holodeckb2b.org/examples/agreement0&lt;/AgreementRef>

Where the outbound MMD had

<AgreementRef pmode="ex-pm-push"/>

Duplicate occurrence of eb3:PayloadInfo elements in single XML delivery

When using the single_xml format the XML document contains duplicate occurrences of the eb3:PayloadInfo elements. The second occurrence contains the modified eb3:PartInfo elements with the additional org:holodeckb2b:ref part property. There should however be just one occurrence of these elements that includes this additional property.

Namespace declararion missing in single XML delivery

When a User Message unit is delivered in the single_xml format there is no default namespace declaration on the root element.