You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <ui...@incubator.apache.org> on 2008/04/07 17:43:25 UTC
[jira] Assigned: (UIMA-964) While handling InvalidMessage UIMA-AS
error handler uses wrong API to extract CAS Ref Id
[ https://issues.apache.org/jira/browse/UIMA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor reassigned UIMA-964:
-----------------------------------
Assignee: Marshall Schor
> While handling InvalidMessage UIMA-AS error handler uses wrong API to extract CAS Ref Id
> ----------------------------------------------------------------------------------------
>
> Key: UIMA-964
> URL: https://issues.apache.org/jira/browse/UIMA-964
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Marshall Schor
> Attachments: uimaj-as-core-UIMA-964-patch.txt
>
>
> HandlerBase.java method populateErrorContext() uses invalid API to extract a CAS Reference Id from a jms message:
> It calls getMessageIntProperty() insteadof getMessageStringProperty()
> errorContext.add( AsynchAEMessage.CasReference, aMessageCtx.getMessageIntProperty(AsynchAEMessage.CasReference));
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.