[
https://issues.apache.org/jira/browse/UIMA-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik updated UIMA-925:
-------------------------------
Attachment: uimaj-as-jms-UIMA-925-patch.txt
uimaj-as-core-UIMA-925-patch.txt
uimaj-as-activemq-UIMA-925-patch.txt
Modified client code to include CasReference ids in listener
entityProcessComplete() callbacks. This facilitates correlation of replies with
requests, especially while handling exceptions. Application may cache a
CasReference id returned from the sendCas() and correlate it with a reply
received via callback. In entityProcessComplete() method the application must
test if the second parameter is of type UimaASProcessStatus and if so may
typecast the parameter to fetch the CasReferenceId associated with the reply
msg.
> How does a UIMA-AS client using sendCAS associate a returned error with the
> CAS that caused it?
> -----------------------------------------------------------------------------------------------
>
> Key: UIMA-925
> URL: https://issues.apache.org/jira/browse/UIMA-925
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.2.1
> Reporter: Burn Lewis
> Priority: Minor
> Fix For: 2.2.2S
>
> Attachments: uimaj-as-activemq-UIMA-925-patch.txt,
> uimaj-as-core-UIMA-925-patch.txt, uimaj-as-jms-UIMA-925-patch.txt
>
>
> When using the UIMA-AS client 'sendCAS' api a unique ID is returned but there
> is no explanation of how this may be used. When an error is returned to the
> UimaASStatusCallbackListener there does not appear to be a way to tell from
> the EntityProcessStatus which of the input CASes failed. Since they are sent
> asynchronously they and their errors may be returned out of order.
> void entityProcessComplete ( org.apache.uima.cas.CAS aCas,
> org.apache.uima.collection.EntityProcessStatus aStatus )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
