Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of paulmcmahan@gmail.com designates
 66.249.92.168 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Nj+uOETdVld4fEYx+8n2xGSSXMswtiUOS5k2UX/0v0NK8Lm+fq6+B5UV0/8ThNyruy+YXuoRtkSKSch7KyAcoELMwhaQGDqSmPjr3qb5FnLZ1nzRI0XtB54SJv60K2+P/4e+zuA3rixzD+r+rFY0/3nCa2bfYgrmq/QFyQcvN3I=
Message-ID: <21df75940608160720j68ee0bbse0081a61395fdf8a@mail.gmail.com>
Date: Wed, 16 Aug 2006 10:20:17 -0400
From: "Paul McMahan" <paulmcmahan@gmail.com>
To: dev@geronimo.apache.org
Subject: Re: Possible blocker for 1.1.1 -- console broken
In-Reply-To: <74e15baa0608160715t2d26ae78g80b4a56efc5a4228@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <7878B282-0BE8-4B15-9B97-095849382D3C@yahoo.com>
	 <40EC0F52-8151-4359-A0C1-2A60623A366D@gmail.com>
	 <74e15baa0608160715t2d26ae78g80b4a56efc5a4228@mail.gmail.com>

I only saw the problem in Jetty.  Tomcat seems to work OK.  May have
to do with the way that Jetty encodes URLs.  But I stopped looking
last night when I saw that Alan had a solution in hand.


Paul


On 8/16/06, Aaron Mulder <ammulder@alumni.princeton.edu> wrote:
> On 8/16/06, Kevan Miller <kevan.miller@gmail.com> wrote:
> > I don't think that it's a blocker. Could be fixed in 1.1.2...
>
> I disagree -- if this is the JACC issue Alan is working on, it makes
> it impossible to create a database pool in the console.  (Though maybe
> there are two separate issues here, because I never got to the point
> of entering a colon)
>
> Thanks,
>      Aaron
>
> > On Aug 15, 2006, at 9:43 PM, David Jencks wrote:
> > Bill Dudney found a problem with the console -- see GERONIMO-2326
> >
> > I've been able to reproduce it on branches/1.1 so I expect it is also  a
> > problem on 1.1.1.  I think the problem only occurs when you try to deploy a
> > non-xa driver, which then includes a database url with lots of colons in the
> > servlet/portlet url.  These colons don't work with the new fixes alan put in
> > to the web app security.
> >
> > I think the solution is to encode the db urls, but I'm not sure when the url
> > is being constructed nor if the encoding should be our responsibility or
> > pluto's   If any console experts such as  Aaron have any ideas that would be
> > great.
> >
> > As a completely separate issue it looks like the work in rev 412804 did not
> > make it into trunk... I'm getting worried about drift between the versions.
> >
> > thanks
> > david jencks
> >
> >
> >
>