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 <[EMAIL PROTECTED]> wrote:
On 8/16/06, Kevan Miller <[EMAIL PROTECTED]> 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
>
>
>
