RbelFacet (tiger-rbel 1.3.1 API)

All Known Implementing Classes:

RbelAsn1Facet, RbelAsn1TaggedValueFacet, RbelAsn1UnparsedBytesFacet, RbelBase64Facet, RbelBearerTokenFacet, RbelBinaryFacet, RbelCetpFacet, RbelHostnameFacet, RbelHttpFormDataFacet, RbelHttpHeaderFacet, RbelHttpMessageFacet, RbelHttpRequestFacet, RbelHttpResponseFacet, RbelJsonFacet, RbelJweEncryptionInfo, RbelJweFacet, RbelJwtFacet, RbelJwtSignature, RbelListFacet, RbelMapFacet, RbelMessageTimingFacet, RbelMtomFacet, RbelNestedFacet, RbelNoteFacet, RbelRequestFacet, RbelResponseFacet, RbelRootFacet, RbelSicctCommandFacet, RbelSicctEnvelopeFacet, RbelSicctHeaderFacet, RbelTcpIpMessageFacet, RbelUndecipherableVauEpaFacet, RbelUriFacet, RbelUriParameterFacet, RbelValueFacet, RbelVauEpaFacet, RbelVauErpFacet, RbelX509Facet, RbelXmlAttributeFacet, RbelXmlFacet
```
public interface RbelFacet
```
Represents a possible interpretation of a RbelElement. This can be both an interpretation of the actual data present in the RbelElement or metadata.

Method Summary

All Methods Instance Methods Abstract Methods Default Methods
Modifier and Type	Method	Description
`RbelMultiMap<RbelElement>`	`getChildElements()`	Child elements for this facet.
`default boolean`	`shouldExpectReplyMessage()`	When parsing a message this gives feedback if we can expect a paired response-message to be transmitted.

- Method Detail
  - getChildElements
```
RbelMultiMap<RbelElement> getChildElements()
```
    Child elements for this facet. The content of the child elements should always be directly or indirectly be taken from the parent element of this facet (e.g. decrypted data is acceptable).
    
    Returns:
    
    A map containing all child elements along with their name (key)
  - shouldExpectReplyMessage
```
default boolean shouldExpectReplyMessage()
```
    When parsing a message this gives feedback if we can expect a paired response-message to be transmitted. (would be true for an HTTP-Request, false for HTTP-Response, false for a STOMP-message...). Will consequently be false for all non-message-protocols. (When we encounter a stray JSON-message directly transmitted via TCP we should not expect the server to send a reply).
    
    Returns:
    
    Whether we should expect a reply message.