Class CommunicationEngineHandler
java.lang.Object
com.aquima.interactions.portal.model.session.CommunicationEngineHandler
- All Implemented Interfaces:
ICommunicationEngineHandler
,ISystemMessagesHandler
Internal communication engine handler to delegate calls to dynamic schema element with a portal engine context.
- Since:
- 9.0
- Author:
- Jon van Leuven
-
Constructor Summary
ConstructorsModifierConstructorDescriptionprotected
-
Method Summary
Modifier and TypeMethodDescriptioncomposeElement
(IElementReference customSchemaElement, InferenceContext profile) This method is called by the communication engine when a custom schema element is encountered and should be composed.void
composeElement
(String customSchemaElement, InferenceContext profile, ICustomElementComposerContext composerContext) This method is called by the communication engine when a custom schema element is encountered and should be composed.boolean
This method will check if a message exists for the specified id.Returns the mime type used by the default serializer.getMessage
(String id) This method returns the message object belonging to the specified id.getMessage
(String id, String... parameters) This method returns the message object belonging to the specified id.getSerializer
(String mimeType) Returns a serializer for the specified mime type.
-
Constructor Details
-
CommunicationEngineHandler
-
-
Method Details
-
composeElement
public void composeElement(String customSchemaElement, InferenceContext profile, ICustomElementComposerContext composerContext) Description copied from interface:ICommunicationEngineHandler
This method is called by the communication engine when a custom schema element is encountered and should be composed.- Specified by:
composeElement
in interfaceICommunicationEngineHandler
- Parameters:
customSchemaElement
- The name of the custom schema element, never null.profile
- The current profile context, never nullcomposerContext
- The custom element composer context that should be used to compose the custom element, never null
-
composeElement
Description copied from interface:ICommunicationEngineHandler
This method is called by the communication engine when a custom schema element is encountered and should be composed.- Specified by:
composeElement
in interfaceICommunicationEngineHandler
- Parameters:
customSchemaElement
- - theIElementReference
of the custom schema, never nullprofile
- - The current profile context, never null- Returns:
- the data value representing the composed custom schema element
-
getSerializer
Description copied from interface:ICommunicationEngineHandler
Returns a serializer for the specified mime type.- Specified by:
getSerializer
in interfaceICommunicationEngineHandler
- Parameters:
mimeType
- The mime type to use, or null for the default serializer.- Returns:
- The data serializer, returns null if no serializer is available for the mimeType.
-
getDefaultSerializerMimeType
Description copied from interface:ICommunicationEngineHandler
Returns the mime type used by the default serializer.- Specified by:
getDefaultSerializerMimeType
in interfaceICommunicationEngineHandler
- Returns:
- the mime type of the default serializer
-
containsMessage
Description copied from interface:ISystemMessagesHandler
This method will check if a message exists for the specified id. The id is not case sensitive.- Specified by:
containsMessage
in interfaceISystemMessagesHandler
- Parameters:
id
- String containing the name (id)- Returns:
- Boolean indicating if a message is defined for the specified id.
-
getMessage
Description copied from interface:ISystemMessagesHandler
This method returns the message object belonging to the specified id. When no message could be found for the given id an UnknownMessageException is thrown.- Specified by:
getMessage
in interfaceISystemMessagesHandler
- Parameters:
id
- Identifier of the message that is requested.- Returns:
- Message object for the specified id.
-
getMessage
Description copied from interface:ISystemMessagesHandler
This method returns the message object belonging to the specified id. With parameters. these parameters are inserted in the message, when the message string contains {} expressions. For example: a message definition of test=Test message with 3 parameters namely: {0}, {1} and {2} will result in the expanded message. When no message could be found for the given id an UnknownMessageException is thrown.- Specified by:
getMessage
in interfaceISystemMessagesHandler
- Parameters:
id
- Identifier of the message that is requested.parameters
- Array of parameter values that should be used in the message.- Returns:
- Message object for the specified id.
-