Hi,
This is I think a plain and simple bug.
Here's the Jira I created: https://issues.apache.org/jira/browse/UIMA-3396
I'll do a fix...
-Marshall
On 10/30/2013 9:11 AM, Eddie Epstein wrote:
Other than reordering the CAS within an annotator via CAS
serialization/deserialization, nothing else
Other than reordering the CAS within an annotator via CAS
serialization/deserialization, nothing else comes to mind. So the next idea
would be to pursue a UIMA bug.
Looking at the exception stack shows the problem is associated with
deleting an FS from the index repository. Code in ruta-core does
Hi Peter,
Things like XmiCasDeserializer.deserialize(new FileInputStream(each), cas,
true) in RutaInterpreterRunner?
I am only looking for things that would do something unexpected to a CAS. I
would not be so concerned with the new Ruta annotations as with changes to
previously existing
Assuming you would rather not share the CAS files, what I'd be looking for
is the xmi:id values changing between the before and after files. There is
some code in ruta that replaces CASes with serialization from files which
could be the cause of this problem.
Eddie
On Tue, Oct 22, 2013 at 10:21
No, this is not an easily reproduced error: I have noticed it so far
only upon application of typesystem-specific ruta rules. I will try to
come up with an easily reproducible example.
In the meantime, I followed your suggestions and added 2 XMI
serialization calls at the end of the AE
Can you share the before and after XmiCas files for a case where UIMA-AS
service serialization failed? No confidential info please!
Eddie
On Tue, Oct 22, 2013 at 2:27 AM, Prokopis Prokopidis proko...@ilsp.grwrote:
No, this is not an easily reproduced error: I have noticed it so far only
Is this a solid error that is easily reproduced?
The error is occurring when UIMA-AS is returning the CAS from the service.
You could add XMI serialization to file at the end of AE processing, for
the good and failing cases. If so lucky to have that serialization fail
too, could try inserting the
Hi all,
I have an AE that produces the error below when deployed as a UIMA-AS
2.4.0 service. The same AE as part of a UIMA 2.4.2 CPE or a uimafit 2.*
pipeline does not produce any errors and works as expected.
Among other things, this AE uses ruta rules to process the CAS. When the
rules
