Uses of Package
com.helger.phase4.messaging
Packages that use com.helger.phase4.messaging
Package
Description
-
Classes in com.helger.phase4.messaging used by com.helger.phase4.clientClassDescriptionThis interface lets you access optional metadata for a single incoming message.
SeeAS4MessagingHelperfor 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. -
Classes in com.helger.phase4.messaging used by com.helger.phase4.dumpClassDescriptionMessage mode.
Was originally calledEAS4IncomingMessageModeuntil v1.2.0.This interface lets you access optional metadata for a single incoming message.
SeeAS4MessagingHelperfor 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. -
Classes in com.helger.phase4.messaging used by com.helger.phase4.incoming.spiClassDescriptionThis interface lets you access optional metadata for a single incoming message.
SeeAS4MessagingHelperfor 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. -
Classes in com.helger.phase4.messaging used by com.helger.phase4.messagingClassDescriptionMessage mode.
Was originally calledEAS4IncomingMessageModeuntil v1.2.0.This interface lets you access optional metadata for a single incoming message.
SeeAS4MessagingHelperfor 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. -
Classes in com.helger.phase4.messaging used by com.helger.phase4.profileClassDescriptionThis interface lets you access optional metadata for a single incoming message.
SeeAS4MessagingHelperfor 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. -
Classes in com.helger.phase4.messaging used by com.helger.phase4.servletClassDescriptionMessage mode.
Was originally calledEAS4IncomingMessageModeuntil v1.2.0.This interface lets you access optional metadata for a single incoming message.
SeeAS4MessagingHelperfor 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. -
Classes in com.helger.phase4.messaging used by com.helger.phase4.servlet.spiClassDescriptionThis interface lets you access optional metadata for a single incoming message.
SeeAS4MessagingHelperfor 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.