Re: TypePriorities configured in the descriptor of an aggregate engine are not added in uima-as

[Jaroslaw Cwiklik]

Thanks Nelson for testing this change. I will commit it soon.
Jerry

On Wed, Aug 30, 2017 at 1:57 PM, nelson rivera 
wrote:

> jerry , i tested the new snapshot of uima-as that you pushed into
> apache snapshot repo to fix problem with the type priorities, and the
> problem is solved. I tested with uima as service with priority
> configuration in the aggregate's descriptor and every things is ok.
> thanks for your quick attention
>
> 2017-08-25 16:47 GMT-04:00, Jaroslaw Cwiklik :
> > Nelson, I just pushed a new snapshot of uima-as to apache snapshot repo.
> > This is a trunk level code not a release. Please deploy it and see if the
> > problem with the type priorites is fixed. I did test it with a simple
> type
> > priority configuration.
> >
> > https://repository.apache.org/content/repositories/
> snapshots/org/apache/uima/uima-as/2.9.1-SNAPSHOT/uima-
> as-2.9.1-20170825.204106-5.tar.gz
> >
> > Jerry
> >
> >
> > On Fri, Aug 25, 2017 at 8:25 AM, nelson rivera  >
> > wrote:
> >
> >> Thanks for your attention Jerry, i wait the solution to integrate it
> >> in production
> >>
> >> 2017-08-24 14:27 GMT-04:00, Jaroslaw Cwiklik :
> >> > Nelson, I was able to recreate this problem and am working on a fix
> >> > now.
> >> > Jerry
> >> >
> >> > On Wed, Aug 16, 2017 at 3:39 PM, nelson rivera
> >> >  >> >
> >> > wrote:
> >> >
> >> >> Jerry, i understand and wait. Thanks for your attention.
> >> >>
> >> >> 2017-08-16 15:09 GMT-04:00, Jaroslaw Cwiklik :
> >> >> > Nelson, I need more time to look into this. Quite busy at a moment.
> >> >> Unless
> >> >> > someone else wants to jump in here I will address the problem when
> I
> >> am
> >> >> > done with current work load,
> >> >> >
> >> >> > Jerry
> >> >> >
> >> >> > On Mon, Aug 14, 2017 at 4:36 PM, Jaroslaw Cwiklik
> >> >> >  >> >
> >> >> > wrote:
> >> >> >
> >> >> >> Thanks, I will try to test this scenario and get back to ya.
> >> >> >>
> >> >> >> Jerry
> >> >> >>
> >> >> >> On Mon, Aug 14, 2017 at 4:27 PM, nelson rivera <
> >> >> nelsonriver...@gmail.com>
> >> >> >> wrote:
> >> >> >>
> >> >> >>> Yes, that is happening
> >> >> >>>
> >> >> >>> 2017-08-14 15:40 GMT-04:00, Jaroslaw Cwiklik  >:
> >> >> >>> > Please confirm that this is happening:
> >> >> >>> >
> >> >> >>> > 1) You deploy an aggregate and specify TypePriorities in
> >> >> >>> > aggregate
> >> >> >>> analysis
> >> >> >>> > engine descriptor.
> >> >> >>> > 2) After uima-as client initilizes, you call client's
> >> >> >>> > public ProcessingResourceMetaData getMetaData();
> >> >> >>> > 3) You check the returned meta and the type priorities are
> >> >> >>> > missing
> >> >> >>> >
> >> >> >>> > You are observing correct behavior when you declare type
> >> priorities
> >> >> in
> >> >> >>> > a delegate analysis engine descriptor of the aggregate
> >> >> >>> >
> >> >> >>> > Jerry
> >> >> >>> >
> >> >> >>> > On Fri, Aug 11, 2017 at 12:12 PM, nelson rivera <
> >> >> >>> nelsonriver...@gmail.com>
> >> >> >>> > wrote:
> >> >> >>> >
> >> >> >>> >> i have configured a priorityList in the descriptor of my
> >> aggregate
> >> >> >>> >> engine, with the objetive of use correctly subiterator()
> >> >> >>> >> function
> >> >> >>> >> in
> >> >> >>> >> my client code over the result CAS.
> >> >> >>> >>
> >> >> >>> >> After deploy the aggregate in uima-as, in my client code that
> >> >> >>> >> consumes
> >> >> >>> >> de uima-as service aggregate to check the priorityList
> >> >> >>> >> configured
> >> >> >>> >> i
> >> >> >>> >> use the instruccion
> >> >> >>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities(); and
> >> not
> >> >> >>> >> appear the priority configured. This does that the use of
> >> >> subiterator
> >> >> >>> >> not have the expected behavior in the uima-as client.
> >> >> >>> >>
> >> >> >>> >> If the configuration of priorityList is made in the descriptor
> >> >> >>> >> of
> >> >> one
> >> >> >>> >> of the delegate of the aggregate, then if the instruccion
> >> >> >>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities()   in
> >> >> client
> >> >> >>> >> code shows the priorityList configured and then the  behavior
> >> >> >>> >> is
> >> >> >>> >> the
> >> >> >>> >> expected.
> >> >> >>> >>
> >> >> >>> >
> >> >> >>>
> >> >> >>
> >> >> >>
> >> >> >
> >> >>
> >> >
> >>
> >
>

Re: TypePriorities configured in the descriptor of an aggregate engine are not added in uima-as

[nelson rivera]

jerry , i tested the new snapshot of uima-as that you pushed into
apache snapshot repo to fix problem with the type priorities, and the
problem is solved. I tested with uima as service with priority
configuration in the aggregate's descriptor and every things is ok.
thanks for your quick attention

2017-08-25 16:47 GMT-04:00, Jaroslaw Cwiklik :
> Nelson, I just pushed a new snapshot of uima-as to apache snapshot repo.
> This is a trunk level code not a release. Please deploy it and see if the
> problem with the type priorites is fixed. I did test it with a simple type
> priority configuration.
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/uima/uima-as/2.9.1-SNAPSHOT/uima-as-2.9.1-20170825.204106-5.tar.gz
>
> Jerry
>
>
> On Fri, Aug 25, 2017 at 8:25 AM, nelson rivera 
> wrote:
>
>> Thanks for your attention Jerry, i wait the solution to integrate it
>> in production
>>
>> 2017-08-24 14:27 GMT-04:00, Jaroslaw Cwiklik :
>> > Nelson, I was able to recreate this problem and am working on a fix
>> > now.
>> > Jerry
>> >
>> > On Wed, Aug 16, 2017 at 3:39 PM, nelson rivera
>> > > >
>> > wrote:
>> >
>> >> Jerry, i understand and wait. Thanks for your attention.
>> >>
>> >> 2017-08-16 15:09 GMT-04:00, Jaroslaw Cwiklik :
>> >> > Nelson, I need more time to look into this. Quite busy at a moment.
>> >> Unless
>> >> > someone else wants to jump in here I will address the problem when I
>> am
>> >> > done with current work load,
>> >> >
>> >> > Jerry
>> >> >
>> >> > On Mon, Aug 14, 2017 at 4:36 PM, Jaroslaw Cwiklik
>> >> > > >
>> >> > wrote:
>> >> >
>> >> >> Thanks, I will try to test this scenario and get back to ya.
>> >> >>
>> >> >> Jerry
>> >> >>
>> >> >> On Mon, Aug 14, 2017 at 4:27 PM, nelson rivera <
>> >> nelsonriver...@gmail.com>
>> >> >> wrote:
>> >> >>
>> >> >>> Yes, that is happening
>> >> >>>
>> >> >>> 2017-08-14 15:40 GMT-04:00, Jaroslaw Cwiklik :
>> >> >>> > Please confirm that this is happening:
>> >> >>> >
>> >> >>> > 1) You deploy an aggregate and specify TypePriorities in
>> >> >>> > aggregate
>> >> >>> analysis
>> >> >>> > engine descriptor.
>> >> >>> > 2) After uima-as client initilizes, you call client's
>> >> >>> > public ProcessingResourceMetaData getMetaData();
>> >> >>> > 3) You check the returned meta and the type priorities are
>> >> >>> > missing
>> >> >>> >
>> >> >>> > You are observing correct behavior when you declare type
>> priorities
>> >> in
>> >> >>> > a delegate analysis engine descriptor of the aggregate
>> >> >>> >
>> >> >>> > Jerry
>> >> >>> >
>> >> >>> > On Fri, Aug 11, 2017 at 12:12 PM, nelson rivera <
>> >> >>> nelsonriver...@gmail.com>
>> >> >>> > wrote:
>> >> >>> >
>> >> >>> >> i have configured a priorityList in the descriptor of my
>> aggregate
>> >> >>> >> engine, with the objetive of use correctly subiterator()
>> >> >>> >> function
>> >> >>> >> in
>> >> >>> >> my client code over the result CAS.
>> >> >>> >>
>> >> >>> >> After deploy the aggregate in uima-as, in my client code that
>> >> >>> >> consumes
>> >> >>> >> de uima-as service aggregate to check the priorityList
>> >> >>> >> configured
>> >> >>> >> i
>> >> >>> >> use the instruccion
>> >> >>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities(); and
>> not
>> >> >>> >> appear the priority configured. This does that the use of
>> >> subiterator
>> >> >>> >> not have the expected behavior in the uima-as client.
>> >> >>> >>
>> >> >>> >> If the configuration of priorityList is made in the descriptor
>> >> >>> >> of
>> >> one
>> >> >>> >> of the delegate of the aggregate, then if the instruccion
>> >> >>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities()   in
>> >> client
>> >> >>> >> code shows the priorityList configured and then the  behavior
>> >> >>> >> is
>> >> >>> >> the
>> >> >>> >> expected.
>> >> >>> >>
>> >> >>> >
>> >> >>>
>> >> >>
>> >> >>
>> >> >
>> >>
>> >
>>
>

Re: TypePriorities configured in the descriptor of an aggregate engine are not added in uima-as

[Jaroslaw Cwiklik]

Nelson, I just pushed a new snapshot of uima-as to apache snapshot repo.
This is a trunk level code not a release. Please deploy it and see if the
problem with the type priorites is fixed. I did test it with a simple type
priority configuration.

https://repository.apache.org/content/repositories/snapshots/org/apache/uima/uima-as/2.9.1-SNAPSHOT/uima-as-2.9.1-20170825.204106-5.tar.gz

Jerry


On Fri, Aug 25, 2017 at 8:25 AM, nelson rivera 
wrote:

> Thanks for your attention Jerry, i wait the solution to integrate it
> in production
>
> 2017-08-24 14:27 GMT-04:00, Jaroslaw Cwiklik :
> > Nelson, I was able to recreate this problem and am working on a fix now.
> > Jerry
> >
> > On Wed, Aug 16, 2017 at 3:39 PM, nelson rivera  >
> > wrote:
> >
> >> Jerry, i understand and wait. Thanks for your attention.
> >>
> >> 2017-08-16 15:09 GMT-04:00, Jaroslaw Cwiklik :
> >> > Nelson, I need more time to look into this. Quite busy at a moment.
> >> Unless
> >> > someone else wants to jump in here I will address the problem when I
> am
> >> > done with current work load,
> >> >
> >> > Jerry
> >> >
> >> > On Mon, Aug 14, 2017 at 4:36 PM, Jaroslaw Cwiklik  >
> >> > wrote:
> >> >
> >> >> Thanks, I will try to test this scenario and get back to ya.
> >> >>
> >> >> Jerry
> >> >>
> >> >> On Mon, Aug 14, 2017 at 4:27 PM, nelson rivera <
> >> nelsonriver...@gmail.com>
> >> >> wrote:
> >> >>
> >> >>> Yes, that is happening
> >> >>>
> >> >>> 2017-08-14 15:40 GMT-04:00, Jaroslaw Cwiklik :
> >> >>> > Please confirm that this is happening:
> >> >>> >
> >> >>> > 1) You deploy an aggregate and specify TypePriorities in aggregate
> >> >>> analysis
> >> >>> > engine descriptor.
> >> >>> > 2) After uima-as client initilizes, you call client's
> >> >>> > public ProcessingResourceMetaData getMetaData();
> >> >>> > 3) You check the returned meta and the type priorities are missing
> >> >>> >
> >> >>> > You are observing correct behavior when you declare type
> priorities
> >> in
> >> >>> > a delegate analysis engine descriptor of the aggregate
> >> >>> >
> >> >>> > Jerry
> >> >>> >
> >> >>> > On Fri, Aug 11, 2017 at 12:12 PM, nelson rivera <
> >> >>> nelsonriver...@gmail.com>
> >> >>> > wrote:
> >> >>> >
> >> >>> >> i have configured a priorityList in the descriptor of my
> aggregate
> >> >>> >> engine, with the objetive of use correctly subiterator() function
> >> >>> >> in
> >> >>> >> my client code over the result CAS.
> >> >>> >>
> >> >>> >> After deploy the aggregate in uima-as, in my client code that
> >> >>> >> consumes
> >> >>> >> de uima-as service aggregate to check the priorityList configured
> >> >>> >> i
> >> >>> >> use the instruccion
> >> >>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities(); and
> not
> >> >>> >> appear the priority configured. This does that the use of
> >> subiterator
> >> >>> >> not have the expected behavior in the uima-as client.
> >> >>> >>
> >> >>> >> If the configuration of priorityList is made in the descriptor of
> >> one
> >> >>> >> of the delegate of the aggregate, then if the instruccion
> >> >>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities()   in
> >> client
> >> >>> >> code shows the priorityList configured and then the  behavior is
> >> >>> >> the
> >> >>> >> expected.
> >> >>> >>
> >> >>> >
> >> >>>
> >> >>
> >> >>
> >> >
> >>
> >
>

Re: TypePriorities configured in the descriptor of an aggregate engine are not added in uima-as

[nelson rivera]

Thanks for your attention Jerry, i wait the solution to integrate it
in production

2017-08-24 14:27 GMT-04:00, Jaroslaw Cwiklik :
> Nelson, I was able to recreate this problem and am working on a fix now.
> Jerry
>
> On Wed, Aug 16, 2017 at 3:39 PM, nelson rivera 
> wrote:
>
>> Jerry, i understand and wait. Thanks for your attention.
>>
>> 2017-08-16 15:09 GMT-04:00, Jaroslaw Cwiklik :
>> > Nelson, I need more time to look into this. Quite busy at a moment.
>> Unless
>> > someone else wants to jump in here I will address the problem when I am
>> > done with current work load,
>> >
>> > Jerry
>> >
>> > On Mon, Aug 14, 2017 at 4:36 PM, Jaroslaw Cwiklik 
>> > wrote:
>> >
>> >> Thanks, I will try to test this scenario and get back to ya.
>> >>
>> >> Jerry
>> >>
>> >> On Mon, Aug 14, 2017 at 4:27 PM, nelson rivera <
>> nelsonriver...@gmail.com>
>> >> wrote:
>> >>
>> >>> Yes, that is happening
>> >>>
>> >>> 2017-08-14 15:40 GMT-04:00, Jaroslaw Cwiklik :
>> >>> > Please confirm that this is happening:
>> >>> >
>> >>> > 1) You deploy an aggregate and specify TypePriorities in aggregate
>> >>> analysis
>> >>> > engine descriptor.
>> >>> > 2) After uima-as client initilizes, you call client's
>> >>> > public ProcessingResourceMetaData getMetaData();
>> >>> > 3) You check the returned meta and the type priorities are missing
>> >>> >
>> >>> > You are observing correct behavior when you declare type priorities
>> in
>> >>> > a delegate analysis engine descriptor of the aggregate
>> >>> >
>> >>> > Jerry
>> >>> >
>> >>> > On Fri, Aug 11, 2017 at 12:12 PM, nelson rivera <
>> >>> nelsonriver...@gmail.com>
>> >>> > wrote:
>> >>> >
>> >>> >> i have configured a priorityList in the descriptor of my aggregate
>> >>> >> engine, with the objetive of use correctly subiterator() function
>> >>> >> in
>> >>> >> my client code over the result CAS.
>> >>> >>
>> >>> >> After deploy the aggregate in uima-as, in my client code that
>> >>> >> consumes
>> >>> >> de uima-as service aggregate to check the priorityList configured
>> >>> >> i
>> >>> >> use the instruccion
>> >>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities(); and not
>> >>> >> appear the priority configured. This does that the use of
>> subiterator
>> >>> >> not have the expected behavior in the uima-as client.
>> >>> >>
>> >>> >> If the configuration of priorityList is made in the descriptor of
>> one
>> >>> >> of the delegate of the aggregate, then if the instruccion
>> >>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities()   in
>> client
>> >>> >> code shows the priorityList configured and then the  behavior is
>> >>> >> the
>> >>> >> expected.
>> >>> >>
>> >>> >
>> >>>
>> >>
>> >>
>> >
>>
>

Re: TypePriorities configured in the descriptor of an aggregate engine are not added in uima-as

[Jaroslaw Cwiklik]

Nelson, I was able to recreate this problem and am working on a fix now.
Jerry

On Wed, Aug 16, 2017 at 3:39 PM, nelson rivera 
wrote:

> Jerry, i understand and wait. Thanks for your attention.
>
> 2017-08-16 15:09 GMT-04:00, Jaroslaw Cwiklik :
> > Nelson, I need more time to look into this. Quite busy at a moment.
> Unless
> > someone else wants to jump in here I will address the problem when I am
> > done with current work load,
> >
> > Jerry
> >
> > On Mon, Aug 14, 2017 at 4:36 PM, Jaroslaw Cwiklik 
> > wrote:
> >
> >> Thanks, I will try to test this scenario and get back to ya.
> >>
> >> Jerry
> >>
> >> On Mon, Aug 14, 2017 at 4:27 PM, nelson rivera <
> nelsonriver...@gmail.com>
> >> wrote:
> >>
> >>> Yes, that is happening
> >>>
> >>> 2017-08-14 15:40 GMT-04:00, Jaroslaw Cwiklik :
> >>> > Please confirm that this is happening:
> >>> >
> >>> > 1) You deploy an aggregate and specify TypePriorities in aggregate
> >>> analysis
> >>> > engine descriptor.
> >>> > 2) After uima-as client initilizes, you call client's
> >>> > public ProcessingResourceMetaData getMetaData();
> >>> > 3) You check the returned meta and the type priorities are missing
> >>> >
> >>> > You are observing correct behavior when you declare type priorities
> in
> >>> > a delegate analysis engine descriptor of the aggregate
> >>> >
> >>> > Jerry
> >>> >
> >>> > On Fri, Aug 11, 2017 at 12:12 PM, nelson rivera <
> >>> nelsonriver...@gmail.com>
> >>> > wrote:
> >>> >
> >>> >> i have configured a priorityList in the descriptor of my aggregate
> >>> >> engine, with the objetive of use correctly subiterator() function in
> >>> >> my client code over the result CAS.
> >>> >>
> >>> >> After deploy the aggregate in uima-as, in my client code that
> >>> >> consumes
> >>> >> de uima-as service aggregate to check the priorityList configured i
> >>> >> use the instruccion
> >>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities(); and not
> >>> >> appear the priority configured. This does that the use of
> subiterator
> >>> >> not have the expected behavior in the uima-as client.
> >>> >>
> >>> >> If the configuration of priorityList is made in the descriptor of
> one
> >>> >> of the delegate of the aggregate, then if the instruccion
> >>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities()   in
> client
> >>> >> code shows the priorityList configured and then the  behavior is the
> >>> >> expected.
> >>> >>
> >>> >
> >>>
> >>
> >>
> >
>

Re: TypePriorities configured in the descriptor of an aggregate engine are not added in uima-as

[nelson rivera]

Jerry, i understand and wait. Thanks for your attention.

2017-08-16 15:09 GMT-04:00, Jaroslaw Cwiklik :
> Nelson, I need more time to look into this. Quite busy at a moment. Unless
> someone else wants to jump in here I will address the problem when I am
> done with current work load,
>
> Jerry
>
> On Mon, Aug 14, 2017 at 4:36 PM, Jaroslaw Cwiklik 
> wrote:
>
>> Thanks, I will try to test this scenario and get back to ya.
>>
>> Jerry
>>
>> On Mon, Aug 14, 2017 at 4:27 PM, nelson rivera 
>> wrote:
>>
>>> Yes, that is happening
>>>
>>> 2017-08-14 15:40 GMT-04:00, Jaroslaw Cwiklik :
>>> > Please confirm that this is happening:
>>> >
>>> > 1) You deploy an aggregate and specify TypePriorities in aggregate
>>> analysis
>>> > engine descriptor.
>>> > 2) After uima-as client initilizes, you call client's
>>> > public ProcessingResourceMetaData getMetaData();
>>> > 3) You check the returned meta and the type priorities are missing
>>> >
>>> > You are observing correct behavior when you declare type priorities in
>>> > a delegate analysis engine descriptor of the aggregate
>>> >
>>> > Jerry
>>> >
>>> > On Fri, Aug 11, 2017 at 12:12 PM, nelson rivera <
>>> nelsonriver...@gmail.com>
>>> > wrote:
>>> >
>>> >> i have configured a priorityList in the descriptor of my aggregate
>>> >> engine, with the objetive of use correctly subiterator() function in
>>> >> my client code over the result CAS.
>>> >>
>>> >> After deploy the aggregate in uima-as, in my client code that
>>> >> consumes
>>> >> de uima-as service aggregate to check the priorityList configured i
>>> >> use the instruccion
>>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities(); and not
>>> >> appear the priority configured. This does that the use of subiterator
>>> >> not have the expected behavior in the uima-as client.
>>> >>
>>> >> If the configuration of priorityList is made in the descriptor of one
>>> >> of the delegate of the aggregate, then if the instruccion
>>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities()   in client
>>> >> code shows the priorityList configured and then the  behavior is the
>>> >> expected.
>>> >>
>>> >
>>>
>>
>>
>

Re: TypePriorities configured in the descriptor of an aggregate engine are not added in uima-as

[Jaroslaw Cwiklik]

Nelson, I need more time to look into this. Quite busy at a moment. Unless
someone else wants to jump in here I will address the problem when I am
done with current work load,

Jerry

On Mon, Aug 14, 2017 at 4:36 PM, Jaroslaw Cwiklik 
wrote:

> Thanks, I will try to test this scenario and get back to ya.
>
> Jerry
>
> On Mon, Aug 14, 2017 at 4:27 PM, nelson rivera 
> wrote:
>
>> Yes, that is happening
>>
>> 2017-08-14 15:40 GMT-04:00, Jaroslaw Cwiklik :
>> > Please confirm that this is happening:
>> >
>> > 1) You deploy an aggregate and specify TypePriorities in aggregate
>> analysis
>> > engine descriptor.
>> > 2) After uima-as client initilizes, you call client's
>> > public ProcessingResourceMetaData getMetaData();
>> > 3) You check the returned meta and the type priorities are missing
>> >
>> > You are observing correct behavior when you declare type priorities in
>> > a delegate analysis engine descriptor of the aggregate
>> >
>> > Jerry
>> >
>> > On Fri, Aug 11, 2017 at 12:12 PM, nelson rivera <
>> nelsonriver...@gmail.com>
>> > wrote:
>> >
>> >> i have configured a priorityList in the descriptor of my aggregate
>> >> engine, with the objetive of use correctly subiterator() function in
>> >> my client code over the result CAS.
>> >>
>> >> After deploy the aggregate in uima-as, in my client code that consumes
>> >> de uima-as service aggregate to check the priorityList configured i
>> >> use the instruccion
>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities(); and not
>> >> appear the priority configured. This does that the use of subiterator
>> >> not have the expected behavior in the uima-as client.
>> >>
>> >> If the configuration of priorityList is made in the descriptor of one
>> >> of the delegate of the aggregate, then if the instruccion
>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities()   in client
>> >> code shows the priorityList configured and then the  behavior is the
>> >> expected.
>> >>
>> >
>>
>
>

Re: TypePriorities configured in the descriptor of an aggregate engine are not added in uima-as

[Jaroslaw Cwiklik]

Thanks, I will try to test this scenario and get back to ya.

Jerry

On Mon, Aug 14, 2017 at 4:27 PM, nelson rivera 
wrote:

> Yes, that is happening
>
> 2017-08-14 15:40 GMT-04:00, Jaroslaw Cwiklik :
> > Please confirm that this is happening:
> >
> > 1) You deploy an aggregate and specify TypePriorities in aggregate
> analysis
> > engine descriptor.
> > 2) After uima-as client initilizes, you call client's
> > public ProcessingResourceMetaData getMetaData();
> > 3) You check the returned meta and the type priorities are missing
> >
> > You are observing correct behavior when you declare type priorities in
> > a delegate analysis engine descriptor of the aggregate
> >
> > Jerry
> >
> > On Fri, Aug 11, 2017 at 12:12 PM, nelson rivera <
> nelsonriver...@gmail.com>
> > wrote:
> >
> >> i have configured a priorityList in the descriptor of my aggregate
> >> engine, with the objetive of use correctly subiterator() function in
> >> my client code over the result CAS.
> >>
> >> After deploy the aggregate in uima-as, in my client code that consumes
> >> de uima-as service aggregate to check the priorityList configured i
> >> use the instruccion
> >> uimaAsynchronousEngine.getMetaData().getTypePriorities(); and not
> >> appear the priority configured. This does that the use of subiterator
> >> not have the expected behavior in the uima-as client.
> >>
> >> If the configuration of priorityList is made in the descriptor of one
> >> of the delegate of the aggregate, then if the instruccion
> >> uimaAsynchronousEngine.getMetaData().getTypePriorities()   in client
> >> code shows the priorityList configured and then the  behavior is the
> >> expected.
> >>
> >
>

Re: TypePriorities configured in the descriptor of an aggregate engine are not added in uima-as

[nelson rivera]

Yes, that is happening

2017-08-14 15:40 GMT-04:00, Jaroslaw Cwiklik :
> Please confirm that this is happening:
>
> 1) You deploy an aggregate and specify TypePriorities in aggregate analysis
> engine descriptor.
> 2) After uima-as client initilizes, you call client's
> public ProcessingResourceMetaData getMetaData();
> 3) You check the returned meta and the type priorities are missing
>
> You are observing correct behavior when you declare type priorities in
> a delegate analysis engine descriptor of the aggregate
>
> Jerry
>
> On Fri, Aug 11, 2017 at 12:12 PM, nelson rivera 
> wrote:
>
>> i have configured a priorityList in the descriptor of my aggregate
>> engine, with the objetive of use correctly subiterator() function in
>> my client code over the result CAS.
>>
>> After deploy the aggregate in uima-as, in my client code that consumes
>> de uima-as service aggregate to check the priorityList configured i
>> use the instruccion
>> uimaAsynchronousEngine.getMetaData().getTypePriorities(); and not
>> appear the priority configured. This does that the use of subiterator
>> not have the expected behavior in the uima-as client.
>>
>> If the configuration of priorityList is made in the descriptor of one
>> of the delegate of the aggregate, then if the instruccion
>> uimaAsynchronousEngine.getMetaData().getTypePriorities()   in client
>> code shows the priorityList configured and then the  behavior is the
>> expected.
>>
>

Re: TypePriorities configured in the descriptor of an aggregate engine are not added in uima-as

[Jaroslaw Cwiklik]

Please confirm that this is happening:

1) You deploy an aggregate and specify TypePriorities in aggregate analysis
engine descriptor.
2) After uima-as client initilizes, you call client's
public ProcessingResourceMetaData getMetaData();
3) You check the returned meta and the type priorities are missing

You are observing correct behavior when you declare type priorities in
a delegate analysis engine descriptor of the aggregate

Jerry

On Fri, Aug 11, 2017 at 12:12 PM, nelson rivera 
wrote:

> i have configured a priorityList in the descriptor of my aggregate
> engine, with the objetive of use correctly subiterator() function in
> my client code over the result CAS.
>
> After deploy the aggregate in uima-as, in my client code that consumes
> de uima-as service aggregate to check the priorityList configured i
> use the instruccion
> uimaAsynchronousEngine.getMetaData().getTypePriorities(); and not
> appear the priority configured. This does that the use of subiterator
> not have the expected behavior in the uima-as client.
>
> If the configuration of priorityList is made in the descriptor of one
> of the delegate of the aggregate, then if the instruccion
> uimaAsynchronousEngine.getMetaData().getTypePriorities()   in client
> code shows the priorityList configured and then the  behavior is the
> expected.
>