uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jens Grivolla <j+...@grivolla.net>
Subject SimpleServer vs. SimpleUimaAsService
Date Thu, 20 Jan 2011 14:37:35 GMT

we are using SimpleServer to create simple interfaces for calling Uima 
pipelines from scripts in various languages, etc.

In order to use UIMA AS services in the same way we are using 
SimpleUimaAsService, but that project is not actively maintained (see 
https://issues.apache.org/jira/browse/UIMA-1918).  We got it to work 
without any code changes by correcting the POM.  It seems to have some 
issues reconnecting when the AS service is restarted, often needing a 
restart of SimpleUimaAsService in Tomcat also.

UIMA AS services can also be used with SimpleServer using JMS 
descriptors, but this doesn't seem to be documented (the official 
documentation talks about using PearPath, the option to point directly 
to a descriptor using DescriptorPath is a bit more hidden).  For this to 
work a few more libs are needed.  We got it to work by including all 
libraries we included for SimpleUimaAsService.

Going forward we need to decide which to use.  Are there advantages to 
using SimpleUimaAsService, or should it simply be deprecated in favor of 
SimpleServer + JMS descriptor?

Two options:
1) drop SimpleUimaAsService, add documentation for SimpleServer + JMS
2) revive SimpleUimaAsService, updating the POM

We have it working both ways, what should we do?

I'm not submitting the patches yet as we haven't updated 
SimpleUimaAsService to the final 2.3.1 release yet, and haven't 
determined exactly what libraries are needed for SimpleServer + JMS in 
order to document that use.


View raw message