Mailing-List: contact user-help@uima.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@uima.apache.org
Received-SPF: pass (nike.apache.org: domain of kottmann@gmail.com designates
 74.125.82.47 as permitted sender)
Message-ID: <51FA60C9.6090903@gmail.com>
Date: Thu, 01 Aug 2013 15:21:13 +0200
From: =?ISO-8859-1?Q?J=F6rn_Kottmann?= <kottmann@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: user@uima.apache.org
Subject: Re: Camel configuration in UIMA-AS
References: <51F60AB6.5080302@orkash.com>
 <CAO329yCuRF3dFD6cQ7=KRCyaD-LmSV59hhmMr8eJc=dor0DjMQ@mail.gmail.com>
In-Reply-To: 
 <CAO329yCuRF3dFD6cQ7=KRCyaD-LmSV59hhmMr8eJc=dor0DjMQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

On 07/29/2013 05:54 PM, Jaroslaw Cwiklik wrote:
> UIMA-AS and Camel integration is described in Chapter 6 Uima Async Scaleut
> document:
>
> http://uima.apache.org/d/uima-as-2.4.0/uima_async_scaleout.html#ugr.async.camel.driver
>
> Its essentially a thin camel wrapper around UIMA-AS client. Its quite dated
> and may not
> work with newer versions of Camel. There is an outstanding JIRA to fix this:
>
> https://issues.apache.org/jira/browse/UIMA-2093

There have been concerns that updating and breaking backward 
compatibility with camel 1.x
might not work for some users, but now camel 1.x is really out dated and 
we should probably
apply the patch to update it.

Just my 2 cents ...

J�rn