Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 72103 invoked from network); 8 Oct 2008 15:39:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Oct 2008 15:39:47 -0000 Received: (qmail 9803 invoked by uid 500); 8 Oct 2008 15:39:44 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 9788 invoked by uid 500); 8 Oct 2008 15:39:44 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 9775 invoked by uid 99); 8 Oct 2008 15:39:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Oct 2008 08:39:44 -0700 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=DNS_FROM_SECURITYSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [209.86.89.65] (HELO elasmtp-kukur.atl.sa.earthlink.net) (209.86.89.65) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Oct 2008 15:38:40 +0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=OJ3s9v4VTaL1hXGzL3SJZ1zZspbShorBd6JGu4bVc3gTw5MrsHySDFR3ngJFHRPN; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [24.40.200.241] (helo=tetra.local) by elasmtp-kukur.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1Knb7l-00031U-DE for user@geronimo.apache.org; Wed, 08 Oct 2008 11:38:53 -0400 Message-ID: <48ECD40C.8030403@earthlink.net> Date: Wed, 08 Oct 2008 11:38:52 -0400 From: Joe Bohn User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914) MIME-Version: 1.0 To: user@geronimo.apache.org Subject: Re: Is it work as design? - New jar will be installed in the new repository location after installed "Geronimo Plugins :: Geronimo Server Specific Repository Plugin" References: <19875437.post@talk.nabble.com> <48ECC3B9.2000808@earthlink.net> <48ECC492.6020403@earthlink.net> <48ECCDC2.2050602@earthlink.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: c408501814fc19611aa676d7e74259b7b3291a7d08dfec791dba881413db6284d6085faf1f709111350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 24.40.200.241 X-Virus-Checked: Checked by ClamAV on apache.org Lin Sun wrote: > I thought his note meant that "postgresql jdbc > driver 8.2 should not be installed in var/respository", at least that > is how I read it. :) You could be right. I was assuming that he wanted to leverage the server specific repo since it was installed and the concern was that the war was not deployed to var/repository. Can you clarify Forrest_Xia? Joe > > On Wed, Oct 8, 2008 at 11:12 AM, Joe Bohn wrote: >> Joe Bohn wrote: >>> Joe Bohn wrote: >>>> Forrest_Xia wrote: >>>>> For example, you use automatic download function to install postgresql >>>>> jdbc >>>>> driver 8.2, the driver will be installed in var/respository >>>>> >>>>> But, if you install a war from admin console, it will be just installed >>>>> in >>>>> geronimo_home/repository. >>>>> >>>>> This different behavior is work-as-design? Thanks for any insight! >>>>> >>>>> Found this with AG 2.1.3. >>>> I believe that this is working as designed at the moment ... but it can >>>> certainly be improved. >>>> >>>> When using server specific repositories you must specify the target >>>> repository using the "--target". As noted in the wiki content (see >>>> http://cwiki.apache.org/GMOxDOC21/multiple-repositories.html and scroll down >>>> to "Using the new repository") this is currently only supported from the >>>> command line. Therefore, when you install the war from the admin console >>>> without a specified target it defaults to /repository. >>>> >>>> Try deploying the war using the command line as specified in the wiki. >>> Hmmm ... just saw a note in that same wiki indicating that if no >>> repository is specified the module is deployed to all repositories. Was this >>> your experience? Perhaps the admin console is assuming the first repository >>> and not iterating through all of them ... so there may be a console bug here >>> as well. >>> >> Or ... it could just be that this note is incorrect. I deployed a war using >> the command line without specifying the target and the results were the same >> as with the admin console ... the war was only deployed to the >> /repository. >> >> I'd still recommend using the command line and specify the appropriate >> target to resolve your issue. >> >> Joe >> >> >