[
https://issues.apache.org/jira/browse/UIMA-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-328.
---
Resolution: Later
> CDE - handle case of searching for impl Java class, but the project is not a
> Jav
[
https://issues.apache.org/jira/browse/UIMA-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-1251.
Resolution: Fixed
Fix Version/s: 2.3
Closing at this point with no further testing or investi
[
https://issues.apache.org/jira/browse/UIMA-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-1479:
-
Fix Version/s: 2.3
> Move UIMA-AS out of sandbox, change to an "add-on" packaging style to the cor
[
https://issues.apache.org/jira/browse/UIMA-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740738#action_12740738
]
Marshall Schor commented on UIMA-1306:
--
Thilo and / or Joern - I think you have looked
[
https://issues.apache.org/jira/browse/UIMA-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik reopened UIMA-1439:
-
Fix a hang in the service listener that prevents the listener from stopping.
ActiveMQ Scheduler threa
I'd like to freeze in 3 weeks, if that is reasonable. For all of you
with code that you want to have in the release, is 3 weeks (Aug 28 - a
Friday) too soon to freeze (stop developing, and see if we can cut a
release candidate)?
This means:
coding of any new things is done, tests written, and e
getViewIterator in CASImpl is written with the signature:
Iterator getViewIterator()
If you are working with things needing CASImpl objects, you would write:
Iterator s = aCas.getViewIterator();
while (s.hasNext()) {
CASImpl ci = (CASImpl) s.next();
... code using ci...
}
If we
The createFilteredIterator method in CASImpl takes an FSIterator and an
FSMatchConstraint, and returns another iterator.
The generification of this is:
public FSIterator
createFilteredIterator(FSIterator it, FSMatchConstraint cons) {
return new FilteredIterator(it, cons);}
This means that t
Jörn Kottmann wrote:
> Marshall Schor wrote:
>> A user had written this:
>>
>> public static Iterator annotationsIterator(
>> JCas aJCas, int type) {
>> return aJCas.getAnnotationIndex(type).iterator(); // fails, cannot
>> convert from FSIterator to Iterator
>> }
>>
>> This compil
Jörn Kottmann wrote:
> Thilo Goetz wrote:
>> Yes, AnnotationBaseFS has no built-in support in UIMA, afaik. The
>> annotation indexes only work on AnnotationFSs.
>>
>> BTW, I'm getting a "unnecessary cast" warning on line 169 of
>> AnnotationIndexImpl, in case anybody goes in there to make those
>>
Marshall Schor wrote:
>
> Thilo Goetz wrote:
[...]
>> I take that back. find() works anyway. The question with
>> moveTo(fs) is simply what the behavior should be in case
>> fs is not in the index. If it is in the index, the cursor
>> will be positioned there, even for bag indexes. If it's
>>
Thilo Goetz wrote:
Yes, AnnotationBaseFS has no built-in support in UIMA, afaik. The
annotation indexes only work on AnnotationFSs.
BTW, I'm getting a "unnecessary cast" warning on line 169 of
AnnotationIndexImpl, in case anybody goes in there to make those
changes.
There must be tons of un
Marshall Schor wrote:
> Thilo Goetz wrote:
>> Eddie Epstein wrote:
>>
>>> Let's pick a date for a first release candidate, say August 28,
>>> and get different people to take responsibility for various packages
>>> to be ready. Then we do a status check on that date to see what
>>> goes forward?
Jörn Kottmann wrote:
> Marshall Schor wrote:
>> A user had written this:
>>
>> public static Iterator annotationsIterator(
>> JCas aJCas, int type) {
>> return aJCas.getAnnotationIndex(type).iterator(); // fails, cannot
>> convert from FSIterator to Iterator
>> }
>>
>> This compile-
Marshall Schor wrote:
A user had written this:
public static Iterator annotationsIterator(
JCas aJCas, int type) {
return aJCas.getAnnotationIndex(type).iterator(); // fails, cannot
convert from FSIterator to Iterator
}
This compile-time error can be eliminated by changing the g
Jörn Kottmann wrote:
>
>> The current choice in generification doesn't support this; a fix would
>> be to change AnnotationIndex generification from
>> public interface AnnotationIndex extends FSIndex to
>> public interface AnnotationIndex extends FSIndex
>>
>> Is this correct?
>>
> The reas
A user had written this:
public static Iterator annotationsIterator(
JCas aJCas, int type) {
return aJCas.getAnnotationIndex(type).iterator(); // fails, cannot
convert from FSIterator to Iterator
}
This compile-time error can be eliminated by changing the generification
of Annotat
The current choice in generification doesn't support this; a fix would
be to change AnnotationIndex generification from
public interface AnnotationIndex extends FSIndex to
public interface AnnotationIndex extends FSIndex
Is this correct?
The reason I choose AnnotationFS was that the java
AnnotationIndex interface extends
FSIndex extends
Iterable.
Iterable interface defines one method,
iterator where T is AnnotationFS (in this case).
AnnotationIndexImpl implements AnnotationIndex.
Therefore, it has a method, iterator, whose return value is
FSIterator.
---
The hi
19 matches
Mail list logo
