Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 7508 invoked from network); 29 Jan 2007 17:09:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Jan 2007 17:09:52 -0000 Received: (qmail 44418 invoked by uid 500); 29 Jan 2007 17:09:55 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 44385 invoked by uid 500); 29 Jan 2007 17:09:55 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 44374 invoked by uid 99); 29 Jan 2007 17:09:55 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Jan 2007 09:09:55 -0800 X-ASF-Spam-Status: No, hits=3.5 required=10.0 tests=FROM_HAS_MIXED_NUMS,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of c1vamsi1c@gmail.com designates 209.85.132.243 as permitted sender) Received: from [209.85.132.243] (HELO an-out-0708.google.com) (209.85.132.243) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Jan 2007 09:09:47 -0800 Received: by an-out-0708.google.com with SMTP id b36so581128ana for ; Mon, 29 Jan 2007 09:09:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=qdxRN0CxuiEfqK3NfYQ2CADMKC1T6OnD+EEMI4uK/zmYlXATHoWZ7jasBJ/tsB+A1NrVmdk+74GUXEfF+K2DsuKSmrntJ2bIeG2OsA2wcQdRNiT3AZJtsCGBeXoOOSrscZsSpzc+EnSL2ft4Xrv7v1SdHelgcNccrMWMZFjg0TQ= Received: by 10.48.254.1 with SMTP id b1mr2686359nfi.1170090564365; Mon, 29 Jan 2007 09:09:24 -0800 (PST) Received: by 10.49.11.8 with HTTP; Mon, 29 Jan 2007 09:09:24 -0800 (PST) Message-ID: <22d56c4d0701290909k76a88348p19353ee31bd6e150@mail.gmail.com> Date: Mon, 29 Jan 2007 22:39:24 +0530 From: "Vamsavardhana Reddy" To: dev@geronimo.apache.org Subject: Re: How to find the context root of a webapp when a EAR is deployed ? In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_258999_11987822.1170090564105" References: <21df75940701281930se2490a8uf054cd021c2c37a@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_258999_11987822.1170090564105 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I guess there is already a JIRA on this. If not, it is better to create one to track this. Vamsi On 1/29/07, Prasad Kashyap wrote: > > OK. Can we design it in such a way that the WARs do show up in that > list with maybe just the context root ? It'd be ok if the other > operations are not permitted on such a webapp. > > That will be a huge usability enhancement wherein you can now directly > go to the context root URL of an application.This will be specially > useful for plugins and samples where the user downloads readily > available EARs and deploys them. He doesn't have to have the added > hassle of knowing what the just deployed app's context root is. > > Cheers > Prasad > > On 1/28/07, Paul McMahan wrote: > > I suspect the reason that WARs contained in EARs are not listed in the > > Web App WARs portlet is because the start, stop, restart, and > > uninstall controls would not work as expected. > > > > Best wishes, > > Paul > > > > On 1/28/07, Prasad Kashyap wrote: > > > After the samples application EAR is deployed, it shows up only in the > > > "Application EARs" portlet. > > > > > > It's webapp does not show up in the list of Web App WARs. So one > > > cannot find it's context root (URL) and go to it. > > > > > > Is this by design ? > > > > > > Cheers > > > Prasad > > > > > > ------=_Part_258999_11987822.1170090564105 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I guess there is already a JIRA on this.  If not, it is better to create one to track this.

Vamsi

On 1/29/07, Prasad Kashyap <goyathlay.geronimo@gmail.com> wrote:
OK. Can we design it in such a way that the WARs do show up in that
list with maybe just the context root ? It'd be ok if the other
operations are not permitted on such a webapp.

That will be a huge usability enhancement wherein you can now directly
go to the context root URL of an application.This will be specially
useful for plugins and samples where the user downloads readily
available EARs and deploys them. He doesn't have to have the added
hassle of knowing what the just deployed app's context root is.

Cheers
Prasad

On 1/28/07, Paul McMahan <paulmcmahan@gmail.com> wrote:
> I suspect the reason that WARs contained in EARs are not listed in the
> Web App WARs portlet is because the start, stop, restart, and
> uninstall controls would not work as expected.
>
> Best wishes,
> Paul
>
> On 1/28/07, Prasad Kashyap <goyathlay.geronimo@gmail.com > wrote:
> > After the samples application EAR is deployed, it shows up only in the
> > "Application EARs" portlet.
> >
> > It's webapp does not show up in the list of Web App WARs.  So one
> > cannot find it's context root (URL) and go to it.
> >
> > Is this by design ?
> >
> > Cheers
> > Prasad
> >
>

------=_Part_258999_11987822.1170090564105--