[jira] Resolved: (UIMA-959) Scaleout doc wrongly implies Vinci and AS services can be in same aggregate

["Eddie Epstein (JIRA)" <ui...@incubator.apache.org>]

     [ https://issues.apache.org/jira/browse/UIMA-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eddie Epstein resolved UIMA-959.
--------------------------------

    Resolution: Fixed
      Assignee: Eddie Epstein

Documentation changed to clarify that a Vinci service should not be called from within a UIMA AS service.

> Scaleout doc wrongly implies Vinci and AS services can be in same aggregate
> ---------------------------------------------------------------------------
>
>                 Key: UIMA-959
>                 URL: https://issues.apache.org/jira/browse/UIMA-959
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.2.2AS
>            Reporter: Burn Lewis
>            Assignee: Eddie Epstein
>            Priority: Minor
>         Attachments: UIMA-959.patch
>
>
> In the scaleout doc Section 1.4.5. "Compatibility with earlier version of remoting and scaleout" we say:
> A Vinci client service descriptor can be used in an aggregate descriptor as before, and can
> be used as a primitive analysis engine in a deployment descriptor
> We should qualify this by saying here (or in "known problems") something like "only if invoked from an aggregate that is deployed as an AS primitive"
> If not in an aggregate we get:  
> org.apache.uima.aae.controller.PrimitiveAnalysisEngineController_impl]: Constructor threw exception; nested exception is java.lang.ClassCastException: org.apache.uima.resource.impl.CustomResourceSpecifier_impl incompatible with org.apache.uima.resource.ResourceCreationSpecifier

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.