Uses of Class com.helger.phase4.incoming.spi.AS4SignalMessageProcessorResult (phase4-lib 4.5.1 API)

Packages that use AS4SignalMessageProcessorResult

Package

Description

com.helger.phase4.incoming.spi

Uses of AS4SignalMessageProcessorResult in com.helger.phase4.incoming.spi

Methods in com.helger.phase4.incoming.spi that return AS4SignalMessageProcessorResult

Modifier and Type

Method

Description

static @NonNull AS4SignalMessageProcessorResult

AS4SignalMessageProcessorResult.createFailure()

static @NonNull AS4SignalMessageProcessorResult

AS4SignalMessageProcessorResult.createSuccess()

static @NonNull AS4SignalMessageProcessorResult

AS4SignalMessageProcessorResult.createSuccess(@Nullable com.helger.collection.commons.ICommonsList<WSS4JAttachment> aAttachments, @Nullable String sAsyncResponseURL, @Nullable Ebms3UserMessage aPullReturnUserMessage)

@NonNull AS4SignalMessageProcessorResult

IAS4IncomingMessageProcessorSPI.processAS4SignalMessage(@NonNull IAS4IncomingMessageMetadata aIncomingMessageMetadata, @NonNull com.helger.http.header.HttpHeaderMap aHttpHeaders, @NonNull Ebms3SignalMessage aSignalMessage, @Nullable IPMode aPMode, @NonNull IAS4IncomingMessageState aIncomingState, @NonNull AS4ErrorList aProcessingErrorMessages)

Process incoming AS4 signal message - pull-request and receipt.
Attachment and Payload are not needed since they are allowed, but should not be added to a SignalMessage Because the will be ignored in the MSH - Processing.