To see what typesystem is returned by your service you can turn up the
logging when invoking runRemoteAsyncAE.
In your UIMA_LOGGER_CONFIG_FILE set
org.apache.uima.adapter.jms.client.level = FINEST
and you'll see the service's typesystem as part of the metadata returned to
the client.
~Burn.
This can be done with the XmiCollectionReader in the examples folder. You
may just need to modify its descriptor to address your input files, or you
can copy the deserialization code from
examples/src/org/apache/uima/examples/xmi
~Burn
Frank writes:
>
> Hi,
>
> I am currently trying to load CAS xmi files and create CAS objects, but I
> can't see how to do it.
Have you managed to work it out?
I am trying to do exact the same thing, and i dont have any luck neither.
[
https://issues.apache.org/jira/browse/UIMA-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-1972:
-
Affects Version/s: (was: 2.3.1SDK)
build-parent-pom-1
Fix Versio
move some build steps under apache-release profile
--
Key: UIMA-1972
URL: https://issues.apache.org/jira/browse/UIMA-1972
Project: UIMA
Issue Type: Improvement
Components: Build, Pack
On 12/14/2010 1:23 PM, Marshall Schor wrote:
> Currently, the build-from-sources for UIMA Java SDK, UIMA-AS and Add-ons is
> targeted at two use-cases:
>
> 1) build by UIMA developers for incremental development
>
> 2) build by release managers for releasing (triggered by mvn
> release:prepare/perf
