Return-Path: 
 <uima-user-return-2471-apmail-incubator-uima-user-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-uima-user-archive@minotaur.apache.org
Received: (qmail 5010 invoked from network); 6 Aug 2009 21:47:43 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 6 Aug 2009 21:47:43 -0000
Received: (qmail 65895 invoked by uid 500); 6 Aug 2009 21:47:50 -0000
Delivered-To: apmail-incubator-uima-user-archive@incubator.apache.org
Received: (qmail 65825 invoked by uid 500); 6 Aug 2009 21:47:50 -0000
Mailing-List: contact uima-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:uima-user-help@incubator.apache.org>
List-Unsubscribe: <mailto:uima-user-unsubscribe@incubator.apache.org>
List-Post: <mailto:uima-user@incubator.apache.org>
List-Id: <uima-user.incubator.apache.org>
Reply-To: uima-user@incubator.apache.org
Delivered-To: mailing list uima-user@incubator.apache.org
Received: (qmail 65815 invoked by uid 99); 6 Aug 2009 21:47:50 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2009 21:47:50 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of eaepstein@gmail.com
 designates 74.125.78.149 as permitted sender)
Received: from [74.125.78.149] (HELO ey-out-1920.google.com) (74.125.78.149)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2009 21:47:42 +0000
Received: by ey-out-1920.google.com with SMTP id 13so389875eye.54
        for <uima-user@incubator.apache.org>;
 Thu, 06 Aug 2009 14:47:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        bh=Xs1SWOqU9wdnV8acOS2m5uXgrSaP6uMcLlKAtMhgm7M=;
        b=An1uGuKwwdfVpesWRhP8Uqoy98sNvFMYfgCo3G6VLiN1cuH1bYjiWFFkZdbj23pcim
         PGltiehtgnkwQU7TMBpRSreWQjCXoP7FlmfmaMU+/xXHVcJF47RlLfO7KoxVP3TMzslD
         nNC0S2cT1ea8oldQtJBLgboZwyIrEhdzKSI74=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=QgPbLdGK+icXdf1JynaoEEpEvQJjMmqbuSAzN5Jvf1nk4vHVk/MeMnlnh736kIENz3
         2SEcdBReU6YdTDp8edFyprjKc6S8Yp2jm5/caTdGcns4F8NdOh81BySePY1sKsYvKyDm
         qYoo4ztgcSVq+hn5gsM7KAKURzptLW/DzczJU=
MIME-Version: 1.0
Received: by 10.216.89.141 with SMTP id c13mr64581wef.66.1249595240857; Thu,
	06 Aug 2009 14:47:20 -0700 (PDT)
In-Reply-To: <4A7B4A1D.6030503@gmail.com>
References: <4A4490D7.1040707@gmail.com>
	 <fe44bdb90906261032g35f81f93s5fd6d460d75f3f28@mail.gmail.com>
	 <4A48AB19.6010204@gmail.com>
	 <fe44bdb90907021213gadab69dp5c08a188557661e5@mail.gmail.com>
	 <4A4DCFE0.4@gmail.com>
	 <cd6edfd30907061240s7d5ba848q964fce6e0508b479@mail.gmail.com>
	 <4A7B4A1D.6030503@gmail.com>
Date: Thu, 6 Aug 2009 17:47:20 -0400
Message-ID: <cd6edfd30908061447k5b3ae835pa6133d2a8906ceee@mail.gmail.com>
Subject: Re: PEAR support in UIMA AS ?
From: Eddie Epstein <eaepstein@gmail.com>
To: uima-user@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked by ClamAV on apache.org

Sounds good to me to create a Jira issue for this. Personally I would
not hold up the next release for it, but it should be valuable to
support this in the future.

Implementing this would require changes to dd2spring to recognize a
<pearSpecifier> and pick up the real descriptor(s), similar changes to
the Deployment Descriptor part of the CDE, and then changes to the AS
framework to be able to actually deploy the service in the PEAR custom
environment. This doesn't sound trivial to me ... but I've been wrong
with Pears before.

Eddie

On Thu, Aug 6, 2009 at 5:24 PM, J=F6rn Kottmann<kottmann@gmail.com> wrote:
> Can we open a jira issue for adding PEAR support or is there
> no interest in it ?
>
> J=F6rn
>>>
>>> Has IBM experience with running UIMA AS on a cluster ?
>>>
>>
>> We have a couple different UIMA AS clusters in operation.
>> One wraps a UIMA AS service as a servlet and uses traditional
>> application server infrastructures to distribute the servlet's WAR
>> file, deploy the servlet, etc. The servlet is basically the
>> UIMA_Service class appropriately modified to extend HttpServlet.
>>
>> Another approach uses an NFS file system to share
>> class and jar files, prepares a process definition in the form of a
>> shell script running UIMA_Service, and launches the script via ssh.
>>
>>
>>>
>>> My AAE resources are hosted on a http server and updated frequently. To
>>> get
>>> them on the servers I use a script which downloads the resources with
>>> wget.
>>> Is there a way to make UIMA AS to re-initialize the running AAE instanc=
es
>>> to
>>> load the updated resources ?
>>>
>>
>> No, the individual services have to be stopped, updated and restarted.
>> Of potential interest are changes Jerry recently made to stop UIMA AS
>> services gracefully, so that they stop listening for new requests, finis=
h
>> any in progress, and then terminate. This allows doing a rolling update
>> of a scaled out service without losing overall server functionality.
>> Again, UIMA_Service is the class to look at for this code.
>>
>> Eddie
>>
>
>