Return-Path: X-Original-To: apmail-isis-users-archive@www.apache.org Delivered-To: apmail-isis-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 06DFE17F49 for ; Wed, 26 Aug 2015 12:45:18 +0000 (UTC) Received: (qmail 23008 invoked by uid 500); 26 Aug 2015 12:45:17 -0000 Delivered-To: apmail-isis-users-archive@isis.apache.org Received: (qmail 22979 invoked by uid 500); 26 Aug 2015 12:45:17 -0000 Mailing-List: contact users-help@isis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@isis.apache.org Delivered-To: mailing list users@isis.apache.org Received: (qmail 22968 invoked by uid 99); 26 Aug 2015 12:45:17 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Aug 2015 12:45:17 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 0C793EE31D for ; Wed, 26 Aug 2015 12:45:17 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.1 X-Spam-Level: **** X-Spam-Status: No, score=4.1 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, KAM_COUK=1.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id J73yQWJyPoUO for ; Wed, 26 Aug 2015 12:45:09 +0000 (UTC) Received: from mail-io0-f178.google.com (mail-io0-f178.google.com [209.85.223.178]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 12F6C42F35 for ; Wed, 26 Aug 2015 12:45:09 +0000 (UTC) Received: by iods203 with SMTP id s203so16764868iod.0 for ; Wed, 26 Aug 2015 05:45:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=y//rNWTR3rCDXbAUnee/tfRj+emANnECYcozqLNkFPI=; b=JO+SVWAv3hf6ewR5bc/GrrCmjUOE2TlwU9ise9GZG0FKYzR23B7CSwf60qxyDdKrRh BlPUTGSpoqMSiJoW72Ju++ExVQzOnZV+uO9DBnzbt3bD/KqBnIhA+Qs4MZq+NYAJkaPH iAzy8BxOHPVU/SRGXeFj/NgAQV3Ac4x2imAtzep/lx/oGTwmsqs3tCaciBzIP+26NZl2 LeRUNyu6cydE+0tLG1eRjzYw1bcYNkfTF7oBuYbR1SzfTxr+WLLdgA7UpQunxFEi0A9L oVtBkAg9f0KBSx+h0SOaIvSaHO3QPTvwMFOENroDIQRt1/yUdaLuUKocQr55U6EI3qOs 4/Sw== X-Gm-Message-State: ALoCoQnGxZ1phPxsNXWBEEhFXfJoQ4H0LVch45nIeaWtMCBeQzLyCZ4ibfmSiSWKXPly74mifnAB X-Received: by 10.107.19.94 with SMTP id b91mr3132558ioj.144.1440593108388; Wed, 26 Aug 2015 05:45:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.134.68 with HTTP; Wed, 26 Aug 2015 05:44:48 -0700 (PDT) X-Originating-IP: [193.178.95.4] In-Reply-To: <55DD806B.8040201@pocos.nl> References: <55DC5BCB.4080904@pocos.nl> <55DD806B.8040201@pocos.nl> From: Dan Haywood Date: Wed, 26 Aug 2015 13:44:48 +0100 Message-ID: Subject: Re: Exception while deploying application using (1.9.0-SNAPSHOT) To: users Content-Type: multipart/alternative; boundary=001a113f3c707decc4051e3638bd --001a113f3c707decc4051e3638bd Content-Type: text/plain; charset=UTF-8 On 26 August 2015 at 10:01, Erik de Hair wrote: > Tried this but have no AppManifest setup yet. Will do that. > >> When you say you are running via embedded Tomcat, what do you mean exactly >> (is this mvn tomcat:run or similar?) >> > I was using mvn tomcat7:run-war. We do this is because we have some tokens > in property-files to be replaced by filters (while creating the war) > depending on the target server (development, test, production). > > okay, I'll take a look at this... > What is actually the most common way to run the application during > development with the possibility to modify DB-connection info, hostname, > port etc without keeping them in version control? I could externalize some > configurations but not all, I believe. > The way we do this with Estatio is to override the configuration properties as per [1] An alternative approach is to specify an AppManifest (because the AppManifest can programmatically override all the environment-specific config properties using whatever mechanism it wanted, eg reading an environment variable). I expect that the AppManifest's feature list will grow as we work through the use cases; but what's there is a useful start already. Thx Dan [1] http://isis.apache.org/guides/ug.html#_ug_deployment_externalized-configuration > >> Thx >> Dan >> > --001a113f3c707decc4051e3638bd--