Return-Path: Delivered-To: apmail-incubator-uima-user-archive@locus.apache.org Received: (qmail 57730 invoked from network); 4 Apr 2008 02:26:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Apr 2008 02:26:48 -0000 Received: (qmail 76504 invoked by uid 500); 4 Apr 2008 02:26:48 -0000 Delivered-To: apmail-incubator-uima-user-archive@incubator.apache.org Received: (qmail 76485 invoked by uid 500); 4 Apr 2008 02:26:48 -0000 Mailing-List: contact uima-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: uima-user@incubator.apache.org Delivered-To: mailing list uima-user@incubator.apache.org Received: (qmail 76476 invoked by uid 99); 4 Apr 2008 02:26:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2008 19:26:47 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of eaepstein@gmail.com designates 64.233.184.232 as permitted sender) Received: from [64.233.184.232] (HELO wr-out-0506.google.com) (64.233.184.232) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Apr 2008 02:26:06 +0000 Received: by wr-out-0506.google.com with SMTP id c46so3451945wra.18 for ; Thu, 03 Apr 2008 19:26:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=1fTunUh5N49Cxjro8n1+1IQSesWFi0PwpSF4PBJFaJU=; b=BK2/8zyk+JYouI8O7xZDy6q3SqG1912vpnf3YZOOFWrwzeg3hFsKM7iO3EpTShdRndPDrQVWAZ40mffRlucuLpJv/IVkNMgQ5UEXRcm91LFihoWCoFFanudvcZ4QXtmYLl0pDI/1hKi71JFDGo2u+D3UV1yNMv0i6+cxFztmuec= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=UyxEqgcR6FdL4P/f3ojhncAk8p2TMexkMaRadTYR/OKulecFd1xFbdFL9tOJEf0C+cvxf1W213Dbnokun6uH+lrvnT526bHbRaDkcvfpADDOz4GHXW7+pw5f/bU6udGwAoxgBYsrkCH4rL0JCx+ktwmeHsM21vLah7Zugeb0kng= Received: by 10.115.108.1 with SMTP id k1mr1073004wam.14.1207275977547; Thu, 03 Apr 2008 19:26:17 -0700 (PDT) Received: by 10.114.154.6 with HTTP; Thu, 3 Apr 2008 19:26:17 -0700 (PDT) Message-ID: Date: Thu, 3 Apr 2008 22:26:17 -0400 From: "Eddie Epstein" To: uima-user@incubator.apache.org Subject: Re: Mixing C++ and Java annotators In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2559_6292184.1207275977539" References: X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_2559_6292184.1207275977539 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Thu, Apr 3, 2008 at 8:33 PM, Johansson, Justin (Contractor) < Justin.Johansson@dsto.defence.gov.au> wrote: > Can anyone say if it is currently possibly to add a C++ annotator into a > UIMA Java pipeline. > I have a dummy annotator written in C++ which works within a UIMA C++ > framework. > > Also when inserted into a UIMA Java framework by specifying C++ in the > AE descriptor together with the path to the AE DLL, > the pipeline runs and calls to the C++ initialize and process methods > can be seen. So far so good. > > However when trying to call any methods on the parameters passed to > initialize or process rather ugly access violation > exceptions result. > Yes this all works. Did you try following the steps on "Verifying Your Installation" in $UIMACPP_HOME/README just to see if the sample code works? Is it valid to add a C++ annotator into essentially a Java-based UIMA > pipeline? I imagine that the UIMA would aspire to allow this but > perhaps given the current state of Apache UIMA is it not possible? > > Can the list enlighten me on the general state of Apache UIMA C++ in any > case or is this still early days? > Apache uimacpp has not changed much in the last 9-12 months. It has always been interoperable with Apache uimaj, although there was one Java change in serialization of the CAS definition that required changes on the C++ side to match. The biggest change to uimacpp over this period was to add support for XMI serialization and create a native C++ service wrapper based on XMI and the JMS messaging of UIMA-AS. There will be a 2.2.2 uimacpp release shortly, using vc8 for the Windows binary. We have no experience with newer versions of msvc, nor with 64-builds on Windows. Eddie ------=_Part_2559_6292184.1207275977539--