[
https://issues.apache.org/jira/browse/UIMA-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bhavani Iyer updated UIMA-1096:
-------------------------------
Attachment: UIMA-1096.patch
Fixed the inconsistencies described. One clarification - the default value for
mutiple references allowed is false.
> Incorrect metaData returned when deployed as a separate process
> ---------------------------------------------------------------
>
> Key: UIMA-1096
> URL: https://issues.apache.org/jira/browse/UIMA-1096
> Project: UIMA
> Issue Type: Bug
> Components: C++ Framework
> Reporter: Burn Lewis
> Attachments: UIMA-1096.patch
>
>
> Comparing the getMeta reply from a service deployed as a separate C++ process
> with that from one deployed via JNI I see the following:
> 1)
> A typePriority index key is changed:
> <fsIndexKey> <typePriority/> </fsIndexKey>
> becomes:
> <fsIndexKey> <featureName> </featureName>
> <comparator>standard</comparator> </fsIndexKey>
> 2)
> Invalid xml chars are not escaped, e.g.
> <description> NAMED > NOMINAL > PRONOMINAL.</description>
> becomes
> <description> NAMED > NOMINAL > PRONOMINAL.</description>
> 3)
> The default of
> <multipleReferencesAllowed>true</multipleReferencesAllowed>
> is inserted in many featureDescriptions
> 4)
> These may be bugs in the JNI output: both <typePriorities> and
> <operationalProperties> are only in the JNI reply.
> 5)
> First 2 lines are missing the encoding & xmlns attributes:
> <?xml version="1.0" encoding="UTF-8"?>
> <analysisEngineMetaData
> xmlns="http://uima.apache.org/resourceSpecifier";>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
