I believe prefetch is only valid for the consumer of a queue. This issue was about rejecting it when specified by the producer, i.e. on the input queue for a remote delegate. Would be nice if we can drop prefetch and this confusion.
On Wed, Aug 27, 2008 at 4:13 PM, Eddie Epstein (JIRA) < uima-dev@incubator.apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/UIMA-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626302#action_12626302] > > Eddie Epstein commented on UIMA-1059: > ------------------------------------- > > This may not be an error as one of the alternatives in UIMA-1110 is to > allow prefetch customization for a remote delegate's queue. I suggest > closing this issue and moving the discussion to 1110. > > > dd2spring doesn't reject the prefetch attribute on the inputQueue for a > remore delegate > > > --------------------------------------------------------------------------------------- > > > > Key: UIMA-1059 > > URL: https://issues.apache.org/jira/browse/UIMA-1059 > > Project: UIMA > > Issue Type: Bug > > Components: Async Scaleout > > Reporter: Burn Lewis > > Priority: Minor > > > > prefetch is relevant only for the inputQueue when deploying a service ... > not when specifying remote delegates. > > Currently dd2spring quietly ignores it when on a remote delegate's queue > ... any chance it can report this as an error? > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >