On 12/28/06, Marshall Schor [EMAIL PROTECTED] wrote:
Adam Lally (JIRA) wrote:
I still think that moving the static utility methods from JCasImpl to a new
JCasUtil class might be would be worthwhile. Also there's the trick that EMF
uses: you can't call a method JCas.method() where JCas is an
On 12/29/06, Thilo Goetz [EMAIL PROTECTED] wrote:
Also, I don't feel like second-guessing the OASIS TC at this point. We
have nothing but the Research report to on right now, and every reason
to believe that it will change significantly before morphing into a
standard.
I'm not sure I get
Well, the concrete may not have quite set yet... but here goes:
1. Goals
The following are confusing (or some might say, broken)
(a) the interface CAS can be an interface to either the whole CAS or to a
view. Methods like this are poor:
CAS view = cas.getView(name);
(b) the logic
On 12/29/06, Thilo Goetz [EMAIL PROTECTED] wrote:
I didn't mean ignore; there isn't much to ignore right now ;-) I'm
waiting to jump on any technical discussion that might develop there,
but there is nothing. I don't have the bandwidth to initiate anything
myself. However, I'm certainly
More on hierarchies of implementation objects, and saving the user from
writing dereferencing chains:
Suppose we divide the CAS methods into those which would just not make sense
on the CasView API, and others. In the same spirit of pleasing the
users by avoiding what they
could see as
[ http://issues.apache.org/jira/browse/UIMA-132?page=all ]
Adam Lally closed UIMA-132.
---
Resolution: Fixed
Provide better support for filenames with spaces in resource URL
On 12/29/06, Marshall Schor [EMAIL PROTECTED] wrote:
snip/
It seems to me you will need a CasViewImpl class - this is for the use
case where the user
wants to, e.g., run two iterators together, one iterating over one view,
while the other goes over
another view.
The actual objects that
[
http://issues.apache.org/jira/browse/UIMA-49?page=comments#action_12461446 ]
Adam Lally commented on UIMA-49:
Simple replacement of package names works now. It's basically just a glorified
search-and-replace utility, but has
some special
Adam Lally wrote:
On 12/29/06, Thilo Goetz [EMAIL PROTECTED] wrote:
I didn't mean ignore; there isn't much to ignore right now ;-) I'm
waiting to jump on any technical discussion that might develop there,
but there is nothing. I don't have the bandwidth to initiate anything
myself. However,
So your proposal is to leave things as they are, except that we call
some of the things that we used to call a CAS a CasView. We're not
going to touch how indexing works, at least conceptually. We could
implement this proposal by simply making the CASImpl class implement the
CasView
10 matches
Mail list logo
