Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sun, 18 May 2014 19:39:38 +0000 (UTC)
From: "Christian Ohr (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12701845.1395048602879.487.1400441978133@arcas>
In-Reply-To: <JIRA.12701845.1395048602879@arcas>
References: <JIRA.12701845.1395048602879@arcas>
Subject: [jira] [Commented] (CAMEL-7301) Move to new HAPI API, since the
 current one is being deprecated
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CAMEL-7301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001172#comment-14001172 ] 

Christian Ohr commented on CAMEL-7301:
--------------------------------------

I implemented the upgrade to HAPI 2.2, including use of the new API 

> Move to new HAPI API, since the current one is being deprecated
> ---------------------------------------------------------------
>
>                 Key: CAMEL-7301
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7301
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-hl7
>            Reporter: Richard Kettelerij
>            Priority: Minor
>
> We're currently using the HAPi 2.0 API. In 2.1 HAPI introduced a new API centered around the new HapiContext object. The current API is fully functional but being deprecated. We should eventually move to the new API see http://hl7api.sourceforge.net/upgrade_to_hapi_2_1.html


--
This message was sent by Atlassian JIRA
(v6.2#6252)