All Classes and Interfaces
Class
Description
Abstract AS4 client based on HTTP client
Abstract AS4 client for signal messages with arbitrary content.
Abstract implementation of
IAS4CryptoFactory.Abstract version of
IAS4IncomingDumper that emits all headers on the output stream.Abstract AS4 message implementation
Abstract builder base class with the requirements for all message types.
Abstract implementation of
IAS4OutgoingDumper that always adds the custom headersAbstract builder base class for a Pull Request.
Abstract base implementation of
IAS4RawResponseConsumer to provide basic
customizability.Abstract builder base class for a user message.
Abstract builder base class for a user messages that puts also the main payload in a single MIME
part and NOT in the SOAP body.
Abstract base class with utility methods.
Java class for anonymous complex type
Helper class to send and AS4 message and handle an incoming AS4 response.
Special
SignatureTrustValidator implementation that allows only certificates for
signature verification but not just public keys.The client HTTP message and some metadata.
AS4 client for
AS4ErrorMessage objects.AS4 client for
AS4PullRequestMessage objects.AS4 client for
AS4ReceiptMessage objects.This class correlates the built source message (
AS4ClientBuiltMessage) with the HTTP
response of the passed type (T).AS4 client for
AS4UserMessage objects.This class contains the central phase4 configuration.
phase4 crypto factory settings based on
IConfig.This class contains an implementation of
IAS4CryptoFactory in which case the
KeyStore is available in memory and the settings are NOT read from a file.AS4 encrypt/decrypt parameters
Special exception type for decompression errors.
Default implementation of
IAS4PModeResolver based on an AS4 Profile ID.This class holds the global stream dumpers.
Utility method to read dump files later.
A special job, that removes all entries
This class represents a single "duplication check" item.
Micro type converter for class
AS4DuplicateItem.This is the duplicate checker for avoiding duplicate messages.
This is the duplicate checker for avoiding duplicate messages.
Encryption helper
Special AS4 error summarizing the EbmsError and the HTTP status code.
Builder class for
AS4Error objects.Specific list of
AS4Error objectsAS4 error message.
An Error does not have to be associated with a P-Mode when it is synchronously send back.
An Error does not have to be associated with a P-Mode when it is synchronously send back.
Generic AS4 helper for specification related things.
Turn on/off AS4 HTTP debug logging.
Note: this class will be replaced with something smarter in the future
Note: this class will be replaced with something smarter in the future
Simple file based version of
IAS4IncomingDumper.A simple
IAS4IncomingDumper that can be used for a single transmission and dumps it to
the OutputStream provided in the constructor.Utility methods for incoming AS4 messages.
Callback interface for handling the parsing result.
Messaging helper methods.
Old name before v3:
Old name before v3:
AS4MessagingHelperThis class holds optional metadata for a single incoming request.
This class manages all the
IAS4IncomingMessageProcessorSPI SPI implementations.This class keeps track of the status of an incoming message.
Implementation of
IAS4IncomingProfileSelector taking a constant AS4 profile ID.Default implementation of
IAS4IncomingProfileSelector taking the AS4 profile ID from the
global AS4ProfileSelector.This class manages all the
IAS4IncomingPullRequestProcessorSPI SPI implementations.Default implementation of
IAS4IncomingReceiverConfiguration.Default implementation of
IAS4IncomingSecurityConfiguration.IO related helper classes
Internal WSS4J callback handler to check if a certain key alias is present in the
IAS4CryptoFactory, and if so return the password for accessing it.A specific helper for
KeyStoreAndKeyDescriptorImplementation of
IAS4ManagerFactory creating managers that are in-memory only.Implementation of
IAS4ManagerFactory creating managers that are persisting to disk.This class represents the result of a message processor SPI implementation.
Note: cannot be serializable because WSS4JAttachment is not serializable
Note: cannot be serializable because WSS4JAttachment is not serializable
MicroType converter registry for this project.
Special wrapper around a
MimeMessage with an indicator if the message can be written more
than once.Helper class for MIME message activities.
Old name before v3:
Old name before v3:
MimeMessageCreatorThis represents a single payload for an outgoing message.
Builder class for class
AS4OutgoingAttachment.File based implementation of
IAS4OutgoingDumper.A simple
IAS4OutgoingDumper that can be used for a single transmission and dumps it to
the OutputStream provided in the constructor.Default implementation of
IAS4Profile.AS4 profile manager.
Static helper class for the fallback AS4 profile selection.
AS4 pull request message
Example implementation of
IAS4RawResponseConsumer writing to a file.Callback interface to create a file based on the provided metadata.
AS4 receipt message
Process incoming AS4 transmissions.
A resource manager that keeps track of temporary files and other closables that will be closed
when this manager is closed.
This class contains all the settings necessary to send AS4 messages using the builder pattern.
The default PullRequest builder.
This sending builder enforces the creation of a MIME message by putting the payload as a MIME
part.
This class contains the init method for the server:
The
MetaAS4Manager instance is ensured to be present
The duplicate cleanup job will also be started.
AS4 receiving servlet.
This servlet works only, if a single AS4 profile is present.
This servlet works only, if a single AS4 profile is present.
This class represents the result of a message processor SPI implementation.
Note: cannot be serializable because WSS4JAttachment is not serializable
Note: cannot be serializable because WSS4JAttachment is not serializable
Message signing helper.
AS4 signing parameters
This class represents a single DOM element in a SOAP header with some metadata.
Special
Old name before v3:
MimeMultipart that modifies the Content-Type to add the "type" parameter with the
SOAP versions MIME type.Old name before v3:
AS4SoapMimeMultipart.A specific helper for
TrustStoreDescriptorSpecial
UnifiedResponse class with some sanity methods.AS4 user message
phase4 specific implementation of
WsuIdAllocator.AS4 XML helper methods.
Main handler for the
AS4ServletA generic HTTP POST wrapper based on
IHttpClientProvider and HttpPost.AS4 constants
Constant values for the AS4 cryptography.
SOAP constants for the usage in AS4
Contains application wide constants.
Special DataContentHandler for SOAP 1.2 messages with the special MIME type.
Default PMode configuration Specification from
This PMode is NOT specific to any profile and only present as a fallback.
http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/core/os/ebms_core-3.0-spec-os.pdfThis PMode is NOT specific to any profile and only present as a fallback.
Marshaller for
ReferenceType objects.Defines the allowed AS4 compression modes.
Message mode.
Was originally called
Was originally called
EAS4IncomingMessageMode until v1.2.0.Defines the meta message types.
Specific enumeration with the result error codes of the
Old name before v3:
AbstractAS4UserMessageBuilder.sendMessageAndCheckForReceipt() method.Old name before v3:
ESimpleUserMessageSendResultThis type defines the structure for PartyInfo Definition.
This defines the content structure for identifying the
root ProcessSpecification for which this business signal is being sent.
This type defines the structure for Role Definition.
This defines the content structure for identiying various parameters
pertaining to the business signal.
Java class for AgreementRef complex type
Java class for CollaborationInfo complex type
Java class for Description complex type
Java class for Error complex type
Builder class for
Ebms3ErrorJava class for From complex type
Java class for MessageInfo complex type
Java class for MessageProperties complex type
The eb:Messaging element is the top element of ebMS-3 headers, and it is
placed within the SOAP Header element (either SOAP 1.1 or SOAP 1.2).
Marshaller for
Ebms3Messaging objects.A special XML namespace context that contains all default Ebms3 mappings.
Java class for PartInfo complex type
Java class for PartProperties complex type
Java class for PartyId complex type
Java class for PartyInfo complex type
Java class for PayloadInfo complex type
Java class for Property complex type
Java class for PullRequest complex type
Java class for Receipt complex type
Java class for Schema complex type
Java class for Service complex type
In the core part of ebMS-3 specification, an eb:Signal Message is allowed to
contain eb:MessageInfo and at most one Receipt Signal, at most one eb:PullRequest
element, and/or a series of eb:Error elements.
Marshaller for
Ebms3SignalMessage objects.Java class for To complex type
Java class for UserMessage complex type
Marshaller for
Ebms3UserMessage objects.Generic implementation of
IEbmsError to represent other errors besides
EEbmsError.Enumeration with all message canonicalization algorithms supported when signing.
Enumeration with all message encryption algorithms supported.
This enum contains all signing supported crypto algorithms.
This enum contains all signing supported crypto algorithms.
Enumeration of key agreement methods for XML Encryption.
Enumeration of key derivation functions used in key agreement schemes.
Enumeration of all key encryption algorithms.
Enumeration with all crypto key identification types (how the key identification is transmitted).
Enumeration of key wrap algorithms used in key agreement schemes.
Defines the basic crypto operation mode - either signing and encrypting or signature verifying
and decrypting.
Enumeration with all predefined EBMS errors based on the specs.
EBMS error category enumeration
EBMS error severity with mapping to
IErrorLevel.Translatable error texts for EBMS error messages
Defines the available Message Exchange Patterns (MEPs).
Predefines transport channel bindings.
Messaging operation to use.
Defines the different sendReceipt reply-patterns
Enumeration with all known and supported SOAP versions.
Specifies the different WS Security versions available
Java class for anonymous complex type
Java class for anonymous complex type
This is a specific HTTP client response handler.
Special HTTP entity that reads and writes to a
MimeMessage.An object encapsulating the HTTP retry settings.
Special HttpClient HTTP POST entity that contains a DOM Node as a serialized String.
Read-only interface for an attachment.
Callback interface for AS4 client message creation.
The basic phase4 crypto interface.
Callback interface for modifying the decryption
RequestData WSS4J object.Base interface for a single duplication check item.
Base interface for an AS4 duplication manager
Factory interface for
WSS4JAttachment objects for handling incoming attachments.Interface for dumping incoming requests
Callback interface to create a file based on the provided metadata.
This interface lets you access optional metadata for a single incoming message.
See
Note: it does not contain the AS4 message ID or similar parameters, because instance of the class must also be present for incoming messages that are invalid AS4 message and hence have no AS4 message ID.
See
AS4IncomingHelper for a transformation method of this object to a JSON
representation.Note: it does not contain the AS4 message ID or similar parameters, because instance of the class must also be present for incoming messages that are invalid AS4 message and hence have no AS4 message ID.
Specific callback interface to inform interested entities about the end of processing of an
incoming message.
Note: this interface is NOT called for outgoing messages, as for sending it is clean and deterministic when it is done.
Note: this interface is NOT called for outgoing messages, as for sending it is clean and deterministic when it is done.
Implement this SPI interface to handle incoming messages appropriate.
Name before v3:
Name before v3:
com.helger.phase4.servlet.IAS4ServletMessageProcessorSPIRead-only AS4 message state for incoming messages.
Old name before v3:
Old name before v3:
IAS4MessageStateCallback interface to determine the used AS4 profile of an incoming message.
Implement this SPI interface to handle incoming pull request appropriately and give the servlet
the right PMode back.
Name before v3:
Name before v3:
com.helger.phase4.servlet.spi.IAS4ServletPullRequestProcessorSPIContains some configuration properties for incoming messages.
Interface to configure the security configuration for incoming messages.
Factory for global managers
Base interface for an AS4 message.
Interface for dumping outgoing requests
An extended
IAS4CryptoFactory with the capability to receive a P-Mode that was
successfully resolved during reception phase.Resolve PMode from ID
Base interface for an AS4 profile - a group of settings that outline what features of AS4 are
used.
Base interface for an AS4 profile manager.
PMode provider interface
Base interface for AS4 profile registrar
AS4 profile registrar SPI interface
Generic AS4 profile validator
Specialized interface for the raw HTTP response consumer.
A callback interface to be notified about returned errors.
A synthetic wrapper for an AS4 HTTP response.
Callback to be informed on http retries
A specific helper interface with the sole purpose to be able to interrupt the sending of a
document after all checks are performed.
A specific callback interface to get the effective sending date time
This is a special callback handler that is meant to be used in combination with the Servlet
handler to customize the incoming request handler.
Specialized interface for the EBMS 3 Signal Message consumer.
Specific callback interface for
ValidatingAS4SignalMsgConsumer to handle the results in a
structured way.Callback interface to indicate finalization of async processing.
Interface for providing time stamps.
The precision of all the methods in this class is milliseconds, so that it stays compatible to XML serialization.
The precision of all the methods in this class is milliseconds, so that it stays compatible to XML serialization.
Specialized interface for the EBMS 3 User Message consumer.
Base interface for a canonicalization algorithm.
Base interface for an encryption algorithm.
Base interface for a signing crypto algorithm.
Base interface for a signing crypto algorithm digests.
Interface for a "session key" provider, that is used for encrypting documents.
Base interface for a single EBMS error
Interface for an HTTP POST sender.
MPC - Message Partition Channel
Interface for an MPC (Message Partition Channel) manager
Base read-only interface for a single
PMode.A nice little helper interface to dynamically create new PMode IDs based on Initiator ID and
Responder ID.
Interface for a manager for
PMode objects.Base interface for SOAP header processors that are invoked for incoming messages.
Customize the
WSSecEncrypt object additional to what is possible via the
AS4CryptParams class.Customize the
WSSecSignature object additional to what is possible via the
AS4SigningParams class.A logging implementation of
IAS4SignalMessageValidationResultHandler.Message Exchange Pattern helper
This class contains every method, static variables which are used by more than one message
creating classes in this package.
Java class for anonymous complex type
Represents a single message property.
Meta manager with all known managers.
Default implementation for an MPC
Manager for
MPC objects.Manager for
MPC objects.XML converter for
MPC objects.An output stream that writes to multiple output streams.
Java class for anonymous complex type
Marshaller for
NonRepudiationInformation objects.This object contains factory methods for each
Java content interface and Java element interface
generated in the com.helger.phase4.ebms3header package.
This object contains factory methods for each
Java content interface and Java element interface
generated in the com.helger.phase4.soap11 package.
This object contains factory methods for each
Java content interface and Java element interface
generated in the com.helger.phase4.soap12 package.
A specific implementation of
Logger that allows to customize the message e.g. with prefix
and suffix.phase4 base exception.
Special phase4 incoming exception for inbound errors.
The logging customizer for the phase4 library.
Specific logger factory for the phase4 library that allows an easy customization of log messages.
phase4 base runtime exception.
Default implementation of
IPModeList of addresses in a PMode
JSON converter for
PModeAddressList objects.XML converter for
PModeAddressList objects.JSON converter for objects of class
PMode.Contains the information for a single direction (leg) of a PMode
Business information - This set of parameters only applies to user messages.
JSON converter for objects of class
PModeLegBusinessInformation.XML converter for objects of class
PModeLegBusinessInformation.Error handling - This P-Mode group concerns errors generated by the reception of the message (for
either a User message or a Signal message, unless indicated otherwise) sent over leg 1 of the
MEP.
JSON converter for objects of class
PModeLegErrorHandling.XML converter for objects of class
PModeLegErrorHandling.JSON converter for
PModeLeg.XML converter for
PModeLeg.PMode leg protocol parameters.
JSON converter for objects of class
PModeLegProtocol.XML converter for objects of class
PModeLegProtocol.PMode reliability stuff.
JSON converter for objects of class
PModeLegReliability.XML converter for objects of class
PModeLegReliability.PMode security part.
JSON converter for objects of class
PModeLegSecurity.XML converter for objects of class
PModeLegSecurity.Persisting manager for
PMode objects.Persisting manager for
PMode objects.XML converter for objects of class
PMode.Party within a PMode
JSON converter for objects of class
PModeParty.XML converter for objects of class
PModeParty.A payload part is a data structure that consists of five properties: name (or Content-ID) that is
the part identifier, and can be used as an index in the notation PayloadProfile[]; MIME data type
(
text/xml, application/pdf, etc.); name of the applicable XML Schema
file if the MIME data type is text/xml; maximum size in kilobytes; and a Boolean value indicating
whether the part is expected or optional, within the User message.JSON converter for objects of class
PModePayloadProfile.XML converter for objects of class
PModePayloadProfile.JSON converter for objects of class
PModePayloadService.XML converter for objects of class
PModePayloadService.A property is a data structure that consists of four values: the property name, which can be used
as an identifier of the property (e.g. a required property named "messagetype" can be noted as:
Properties[messagetype].required="true"); the property description; the property
data type; and a Boolean value, indicating whether the property is expected or optional, within
the User message.XML converter for objects of class
PModeProperty.XML converter for objects of class
PModeProperty.JSON converter for objects of class
PModeReceptionAwareness.XML converter for objects of class
PModeReceptionAwareness.A special exception thrown in PMode validation.
Java class for anonymous complex type
Java class for Body complex type
Java class for detail complex type
Java class for Envelope complex type
Marshaller for
Soap11Envelope objects.Fault reporting structure
Java class for Header complex type
A special XML namespace context that contains all default SOAP 1.1 mappings.
Java class for Body complex type
Java class for detail complex type
Java class for Envelope complex type
Marshaller for
Soap12Envelope objects.Fault reporting structure
Java class for faultcode complex type
Java class for faultreason complex type
Elements replacing the wildcard MUST be namespace qualified, but can be in the targetNamespace
A special XML namespace context that contains all default SOAP 1.2 mappings.
Java class for NotUnderstoodType complex type
Java class for reasontext complex type
Java class for subcode complex type
Java class for SupportedEnvType complex type
Java class for UpgradeType complex type
This class manages the EBMS Messaging SOAP header element
This class manages the SOAP header element processors.
This class manages the WSS4J SOAP header
Implement this SPI interface if your JAR file contains external third party modules.
Specific wrapped
IAS4SignalMessageConsumer that verifies the DSig References between the
sent message and received Receipt is identical.Special WSS4J attachment with an InputStream provider instead of a fixed InputStream
Note: cannot be serializable because base class is not serializable and because we're dealing with
Note: cannot be serializable because base class is not serializable and because we're dealing with
InputStreams.A Callback Handler implementation for the case of signing/encrypting Attachments via the SwA
(SOAP with Attachments) specification or when using xop:Include in the case of MTOM.
A utility class to handle the life cycle of the
WSSConfig objects.A helper class to run all WSS stuff in a lock.
Serializes
boolean as 0 or 1.