uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jaroslaw Cwiklik <uim...@gmail.com>
Subject Re: [jira] Commented: (UIMA-1593) AEs that declare multipleDeploymentAllowed=false can't be deployed as services and called from multiple clients in the same JVM
Date Mon, 05 Oct 2009 14:11:06 GMT
it seems to me that this is not just a service wrapper problem. We should
try to override this parameter for all remotes, no?

On Fri, Oct 2, 2009 at 2:15 PM, Marshall Schor (JIRA) <
uima-dev@incubator.apache.org> wrote:

>
>    [
> https://issues.apache.org/jira/browse/UIMA-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761657#action_12761657]
>
> Marshall Schor commented on UIMA-1593:
> --------------------------------------
>
> If we override this value in the service wrapper in all cases, does that
> break anything?  If not, I would be +1 for doing this in the service
> wrapper.
>
> > AEs that declare multipleDeploymentAllowed=false can't be deployed as
> services and called from multiple clients in the same JVM
> >
> -------------------------------------------------------------------------------------------------------------------------------
> >
> >                 Key: UIMA-1593
> >                 URL: https://issues.apache.org/jira/browse/UIMA-1593
> >             Project: UIMA
> >          Issue Type: Bug
> >          Components: Async Scaleout, Core Java Framework
> >    Affects Versions: 2.2.2
> >            Reporter: Adam Lally
> >
> > If an AnalysisEngine descriptor declares multipleDeploymentAllowed=false,
> the intention is that there cannot be multiple instances of it in the same
> JVM.  UIMA reports an error if you try to embed such an AE in an aggregate
> that declares multipleDeploymentAllowed=true.  But this only makes sense for
> co-located components, not services.
> > Currently, the service wrapper returns the
> multipleDeploymentAllowed=false as part of the getMetaData() call.   The
> aggregate AE checks this metadata for consistency, and at that point it
> isn't aware that it came from a service, so the exception is thrown.
> > Perhaps the service wrapper should be modified to set
> mutlipleDeploymentAllowed to true when responding to all getMetaData()
> calls?  Alternatively it could be done on the client side, but to me it
> makes more sense for the service to do it - why expose this setting if
> clients have no use for it?
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message