All notable changes to this project will be documented in this file. This project adheres to Semantic Versioning.
- Incorrectly generated IDs within WS-Security header #98
- Misleading result of PullRequest submission #91
- NPE on first initialization of pull workers #92
- Disk resource leakage when submission fails #94
- Trusted certificate with name constraints extension results in failed processing #97
- The default security provider now uses version 2.2.2 and 2.1.2 of WSS4J and Apache Santuario (xml-sec)
- Support for sending selective pull requests using simple selection items as described in section 5.1 of the
ebMS 3 Part 2 (Advanced Features) specification.
NOTE: In version 4.1.0 the support is limited to sending of selective pull requests with "simple selection items" as described in the specification. Selection criteria are not used when processing received pull requests.
- Added two generic events to indicate that a problem occurred during the processing of a received message
IReceivedMessageProcessingFailure) or a message to be sent (
ISendMessageProcessingFailure). These events are intended for use as "filters" when configuring the event handling. Specific events are available for specific errors. Using the generic events the error reporting defined by the P-Mode parameters
PMode.ErrorHandling.Report.ProcessErrorNotifyProducer and PMode.ErrorHandling.Report.ProcessErrorNotifyConsumer can be implemented.
- Added a new event (
org.holodeckb2b.interfaces.events.IMessageSubmission) to indicate that a User Message or Pull Request message unit was submitted to the Holodeck B2B Core
- Added a new event (
org.holodeckb2b.interfaces.events.IHeaderValidationFailure) to indicate that the validation of the message header failed
- New interfaces for all message processing events without the Event suffix. The old interfaces are still available for backward compatibility, but should not be used anymore (see also below).
- Option to register "global event handlers" in the Holodeck B2B Core. These handlers will be used to process events if the P-Mode does not specify one.
- A Holodeck B2B specific message processing context that holds all information about the message that is processed in the current processing pipeline. Refactored all handler classes to use new context.
- When a pulled User Message cannot be matched to a P-Mode it is assigned to the P-Mode of the Pull Request.
- When no MPC is specified in either P-Mode or submission the default MPC is used for the Pull Request. If an MPC is specified in both the one in the submission must be a sub-channel of the one in the P-Mode.
mpcattribute is not included in a Pull Request when the default MPC is pulled.
- Generalised the header validation handler so it can be more easily reused for other protocols.
- Removed check on empty ConversationId when submitting a User Message to the Core.
- All event implementation classes to use the new event interface names.
- Split handling of errors generated during processing of a received message in two handlers, one bundling the individual errors into Error Signals and one for determining how to report the Error Signals. Allows for re-use of "bundling" handler in different messaging protocols.
- Moved common classes from core to the common module.
- Core submission function now first checks whether the specified payloads can be copied/moved to internal storage before saving the message meta-data. This allows back-end applications to re-submit messages in case there is an error in moving the payloads.
- The interfaces for the message processing events with the Event suffix. They are replaced with interfaces without suffix to shorten the event names and prevent duplication of "event" in the qualified class name.
- Description of processing states could not be saved due to missing API. (In Holodeck B2B 4.0.0.)
- Name of the log used for reporting errors generated during processing of incoming messages included null instead of the message protocol name.
- When no retry configuration is available for a message but a Receipt is expected a MissingReceipt ebMS Error is generated and reported [as configured in the P-Mode] to the business application instead of only logging an error message.
- Integration tests were not executed when running them from the IDE with the
JAVA_HOMEsystem environment variable not set. Now the JVM used by the IDE is used.
- Strict validation of the AgreementRef being a URI in case no type has been specified.
- Exceptions in processing User Messages without payloads.
- Check that P-Mode specified for a submitted Pull Request supports pulling and that there is no conflict in the MPCs specified in both P-Mode and submission.
- _UnsupportedException_s in
org.holodeckb2b.security.results.SignedPartMetadata.TransformMetadatawhen getting algorithm and parameters.
- Issue in finding P-Mode for User Messages when message received could be matched to a P-Mode configured for sending messages based on pull.
- NPE in file delivery of Receipt without content (will only occur when used for non-AS4 Receipts)
- NPE when ebMS3 message is received that contains a WS-Security Signature which does not sign the ebMS message header
(i.e. there is no
ds:Referenceelement for the
- More flexible retry configuration of the AS4 Reception Feature where it is now possible to specify each interval
separately. See refactored
- Option to apply strict validation of ebMS header meta-data. By default Holodeck B2B only validates
that it is able to process the message. When applying strict validation mode it will check that the header
meta-data conforms to all requirements as stated in the ebMS Specifications.
The use of the strict validation mode can be configured both globally on Holodeck B2B instance level
IConfiguation.useStrictHeaderValidation()) or on a per P-Mode basis (
- It is now possible to perform custom validations of User Message message units before delivery to
the Consumer. Depending on the configuration validation problems may result in rejection of the message
unit and return an ebMS Error Signal to the sender of the message. The configuration of the custom validation
is done in the User Message flow of the P-Mode, see
- Check on the correct combination of Service and Action meta-data values when when triggering a "ping test" as defined in the ebMS V3 Core Specification.
- Interfaces for separation of Core functionality and processing of the WS-Security headers in a message by introducing the Holodeck B2B Security Provider concept.
- A default security provider implementation. Similar to the older versions based on the WSS4J libraries but now using seperate keystores for encryption and signature verification certificates.
- Message processing events for delivery attempts of message units and security processing, e.g. signature creation and validation, en-/decryption, etc.
- Option to indicate that a problem in delivery of the message is permanent and an ebMS Error can be returned to the sender of the message.
- Added 'IMessageProcessingState.getDescription()' method so an additional description on the processing state of a message unit can be stored. NOTE: This description is introduced for future use, the Holodeck B2B Core does not yet use it!
- Added optional parameter to
IQueryManager.getMessageUnitsWithId()to indicate that only message units flowing in a specific direction should be returned
- Added default initialization method to
IPModeSetto pass the Holodeck B2B home directory as parameter on creation of the P-Mode storage implementation.
- The default URL path where Holodeck B2B receives AS4 messages and which needs to be used by the Sending MSH has been changed to /holodeckb2b/as4. For backward compatibility the old path msh can still be used, its use however isn't recommended!
- When multiple P-Modes match to a received message this is now considered as "no match found" and no result is returned instead of the first matching P-Mode.
- Refactored the validation of the ebMS header meta-data validation classes and handler to align with custom validation classes.
- Added the Holodeck B2B home directory as parameter to the
- Renamed method
IMessageUnitinto stand alone
- The ebMS Error returned to the sender in case the signature of a User Message does not include all payloads of the message has been changed from ValueInconsistent to PolicyNonCompliance
- Moved classes in
- Refactored package structure of message processing events related interfaces: The definition of all events is done
using interfaces in the
org.holodeckb2b.interfaces.eventsand subpackages. Interfaces related to the processing of events are in
IQueryManager.isAlreadyProcessed()to also take failed message units into account when determining if a user message is already processed and should be considered a duplicate.
- Changed the API specification of the query methods in
IQueryManagerto return empty collections instead of
nullwhen no matching message units have been found
- Changed argument of the
IQueryManager.isAlreadyProcessed()to full message unit instead of just the messageId
- Updated to Axis2 version 1.7.7 and Bouncy Castle version 1.59
- The log name for message processing now includes indication of the message protocol being processed. The message protocol is retrieved from the HandledMessagingProtocol parameter of the engaged Holodeck B2B module.
- Renamed the Axis2 phases that include the handlers for processing the messages to more generic protocolInPhase and protocolOutPhase making easier to install extensions for other messaging protocols.
- Refactored the logging to have clear separation of details logged at the different levels. Using INFO level provides enough information to see all messages which are processed. Going to DEBUG add information of process steps and TRACE provides most detailed logging.
- In case of exception when logging an invalid SOAP message, a error message is written to SOAP log
- The configuration parameter (
IConfiguation.allowSignalBundling()) which was used to indicate that it was allowed to bundle multiple Signal message units of the same type in one message. This goes beyond the ebMS V3 Core and AS4 Specifications and this option is therefore removed.
- The configuration parameter (
IConfiguation.useStrictErrorRefCheck()) to apply a strict validation on the references in the Error signal is replaced by the generic strict header validation mode.
- The configuration parameters (as defined in
IConfiguration) related to the keystores used in WS-Security processing. By enabling compatability mode in the new default security provider the functionality of the old version is still supported.
- The methods
org.holodeckb2b.interfaces.as4.pmode.IReceptionAwarenessas they are superseded by the new
getWaitIntervals()method which allows both fixed and flexible retry configuration. Older implementations of this interface can still be used in this version as it provides default implementations to convert to the new interface.
- The msh URL path for receiving messages. The new /holodeckb2b/as4 path should be used.
IMessageSubmitter.submitMessage(IUserMessage)and corresponding implementation.
IPModeSet.listPModeIds()and corresponding implementation.
- Use 'exec' to start the Java program, instead of forking the process to simplify management of the Java process.
- Updated the example certificates and key stores to extend validity of certificates
- Checking of references in Error Signal has been corrected so Error with the reference contained only in the Errors is not rejected.
- Exception when processing an invalid SOAP message #15
- Updated README regarding certificate management in
repository/certsfolder to include also the keystore with the certificates of trusted certificate authorities.
- Severity attributes should be "warning" or "failure" not "WARNING" or "FAILURE" #89
- Test for
org.holodeckb2b.ebms3.workers.SubmitFromFileworker has been changed due to refactoring
- Skipped MMD files ignored until gateway restart #86
- Notification includes original Receipt content #82
- Incorrect root element in single XML file delivery #83
- No XML schema provided for single XML delivery #84
- Support for the type attribute of both Message and Part Properties. See also issue #2 in the OASIS ebMS TC's issue tracker
- Added the default temp directory to the distribution
- Support for continuously running workers
- Packaged the Holodeck B2B msh service as Axis2 aar file
- Included the Holodeck B2B module meta-data in the Core jar file
- Sending of Pull Requests is now done by the
- Reverted back to version 2.0.4 of Apache Santuario library to fix unknown method issue in case an exception occurs in the XML security processing
- StringIndexOutOfBoundsException when eb:Timestamp does not contain 'Z' indicator #78
- Issue in Receipt processing when the referenced message was not completely loaded from storage but previous processing states need to be evaluated
- Pull Requests directly submitted to the Core are never sent
- Non closed output streams and incorrect flushing of data in file delivery methods
- Refactored database configuration in default persistency module
- Removed database related code from other modules
- Confusing log message in SubmitFromFile worker when MMD file can not be renamed #69
- Body payload(s) not encrypted when message also contains other payloads #70
- P-Mode validation feature which separates the validation of P-Modes from both their internal and external storage
- The direction and processing states of a message unit are now available through the interfaces
- Unit tests to improve test coverage
- Integration tests. These tests set up two Holodeck B2B instances and execute both a push and a pull exchange to check that everything works on run time
- A default implementation of the message model interface (in Common module)
- Interfaces for separation of Core functionality and storage of message unit meta-data
- Default persistency provider implementation
IMessageSubmitter.submitMessage(IUserMessage)method with parameter to indicate whether to delete the original payload files on message submission
- Refactored the validation of received message units into separate validation classes and handler
- Refactored Core module to use new persistency interfaces
- Moved XML message meta-data implementation and ProductId classes to Common module
- It is now possible to not only configure whether Error Signals should be logged but also if all signals
should be logged or only the ones that contain an Error with severity failure (see
log4j2.xmlfor more info)
- The single parameter version of the
IMessageSubmitter.submitMessage(IUserMessage)method has been deprecated. The new version with the additional parameter to indicate whether payload files should be deleted should be used.
org.holodeckb2b.common.exceptions.DuplicateMessageIdErrorwhich were bound to the specific persistency implementation of previous versions
- ebMS errors are only logged when log level is ERROR #35
- Exceptions in processing of WSS header not handled correctly #36
- NPE in CreateSOAPEnvelopeHandler when sending async Error with unknown P-Mode #45
- NPE in purge operation when payload location is not available #46
- P-Mode finding does not take into account MPC defined in PullRequesFlow #47
- NPE in P-Mode finding process when only declaring SecurityConfiguration for a TradingPartner #48
- Server starts with error message if Holodeck B2B directory name includes space #54
- Unable to start on Windows when using very long base path #64
- Resolved build issues in unit tests on Windows platform
- Support for the AS4 Multi-hop feature as specified in section 4 of the AS4 OASIS Standard.
- Event framework to enable additional notification to external components about events that occur during message
org.holodeckb2b.interface.eventsfor the new interfaces.
- Default implementation of message purging. This default implementation will remove all meta-data (including payload data for User Messages) after a configurable number of days has passed since the last change to the message unit's processing state.
- Events for creation of a Receipt (see
org.holodeckb2b.interfaces.events.types.IReceiptCreatedEvent), creation of a signature for a User Message (see
org.holodeckb2b.interfaces.events.types.ISignatureCreatedEvent) and for the removal of an "expired" User Message (see
- A trust store to hold the certificates of trusted Certificate Authorities that are used to validate the certificates used for signing a message. This trust store should be used for certificates not directly related to a trading partner.
- Possibility to configure the Pull Worker Pool from outside the Holodeck B2B Core through the new
- When a received Error signal does not reference a sent message unit a ValueInconsistent error is generated. Note that this can be caused by either an invalid or missing reference in the Error signal.
- The addition of the event framework resulted in changes to the Holodeck B2B Core and P-Modes interfaces to get access to the event processor and enable configuration of event handlers.
- The XML P-Mode implementation was changed to add the event handler configuration, see the new version of the schema in pmode.xsd.
- Pull Requests are now also submitted to the Core. This required a change in the
IMessageSubmitterinterface that now also accepts
IPullRequestobjects for submission. Together with the new ability to configure the pull worker pool it allows extensions to set-up a custom mechanism for triggering the pulling.
- Received ebMS Error signals are now logged to the special error log
org.holodeckb2b.msgproc.errors.receivedregardless whether they can be processed completely or need to be notified to the Producer application.
- Messages without attachments are now sent as single part messages, i.e. not using the SOAP with Attachments feature.
- The bundling of Signal Messages is disabled because it can cause problems in multi-hop exchanges and it is also not widely interop tested. Disabling the bundling is done by removing the handlers that add the signals to the message from the processing flow in the configuration of the Holodeck B2B module. Bundling will be enabled again in a future version.
- PathWatcher does not honour system home directory #19. Thanks @phax.
- Problem with renaming mmd file to result extension if a file with the same name already exists.
- Payload with MIME type "application/gzip" is not decompressed #24.
- Rejected submission when multiple PartyIds were specified in both submission and P-Mode.
Philip Helger for various general code improvements.
- Include derived refToMessageId in Error signal when notifying business application about the error #12.
- PartyId can not be set on submission when security is used #13
- Long error descriptions can not be stored in the database #14
- Identification of Holodeck B2B in User-Agent and Server HTTP headers