You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Marshall Schor <ms...@schor.com> on 2006/11/29 20:14:25 UTC
Use of XCASSerializer in vinci service deployments
The big doc says in the section on how to deploy a UIMA component as a
Vinci service to use a deployment descriptor which contains
<parameter name="serializerClassName"
value="...service.vinci.VinciXCASSerializer_NoDocText"/>
Is this correct still, or is this changing to use XMI in version 2?
-Marshall
Re: Use of XCASSerializer in vinci service deployments
Posted by Marshall Schor <ms...@schor.com>.
Adam Lally wrote:
> On 11/29/06, Marshall Schor <ms...@schor.com> wrote:
>> The big doc says in the section on how to deploy a UIMA component as a
>> Vinci service to use a deployment descriptor which contains
>> <parameter name="serializerClassName"
>> value="...service.vinci.VinciXCASSerializer_NoDocText"/>
>>
>
> Actually I just checked and that parameter is never used anywhere.
> I'll open a JIRA issue to clean that up.
OK. I removed it from the application dev guide docs.
-Marshall
Re: Use of XCASSerializer in vinci service deployments
Posted by Adam Lally <al...@alum.rpi.edu>.
On 11/29/06, Marshall Schor <ms...@schor.com> wrote:
> The big doc says in the section on how to deploy a UIMA component as a
> Vinci service to use a deployment descriptor which contains
> <parameter name="serializerClassName"
> value="...service.vinci.VinciXCASSerializer_NoDocText"/>
>
Actually I just checked and that parameter is never used anywhere.
I'll open a JIRA issue to clean that up.
> Is this correct still, or is this changing to use XMI in version 2?
>
There'a a JIRA issue to implement XMI-based transport adapter, but we
haven't agreed to do this prior to v2.1.
-Adam