[
https://issues.apache.org/jira/browse/UIMA-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik updated UIMA-1271:
--------------------------------
Attachment: uimaj-as-jms-UIMA-1271-patch.txt
uimaj-as-core-UIMA-1271-patch.txt
uimaj-as-activemq-UIMA-1271-patch.txt
Modified client API to always send GetMeta and CPC requests in a TextMessage
instead of BytesMessage. In GetMeta reply, a UIMA AS service provides a new
parameter that indicates that the service supports binary serialization. Binary
serialization will only be used if the client is configured to use binary *AND*
the service advertises support for binary serialization in GetMeta reply.
Old services dont advertise serialization in GetMeta replies and a default
serialization (XMI) will be used. If the client is configured with binary
serialization and uses an old service, the code will override binary
serialization and use XMI instead. A Warning message will appear on the console
as well as in the uima log.
> UIMA-AS Should Use TextMessage Only for GetMeta Request and Reply
> -----------------------------------------------------------------
>
> Key: UIMA-1271
> URL: https://issues.apache.org/jira/browse/UIMA-1271
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: uimaj-as-activemq-UIMA-1271-patch.txt,
> uimaj-as-core-UIMA-1271-patch.txt, uimaj-as-jms-UIMA-1271-patch.txt
>
>
> UIMA-AS is using BytesMessage for getMeta request and response if it is
> configured to use binary serialization. GetMeta messages should always be
> passed in a TextMessage for compatibility with older services. The GetMeta
> reply should also include a flag that indicates service support of binary
> serialization. The client will not use binary serialization (even if is
> configured with binary) if the service says that it doesnt support it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
