cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pier Fumagalli <>
Subject Re: News from the Websphere 5.0 front
Date Mon, 03 Feb 2003 17:07:36 GMT
"Greg Wilkins" <> wrote:
> Peir 

It's Pier :-) :-) :-) (I write it wrong myself 1/2 of the times)

> don't get me started on the stupidity of the servlet specs path mapping!

Well, you know I share your opinion on that! :-)

> I was aware if the difference between the spec and Jetty - but I had not
> changed it as:
> + I am loath to change something that has been that way for a long time.

And that _makes_sense_ IMO! :-)

> + I was waiting to fail a watchdog test in order to force me to do it and
>   have a good reason if users complained.

I don't know if there will ever be a WatchDog test that can actually be
helpful to check the non-trivial part of the spec...

> + I was hoping the spec would correct itself.

You're joking, right? :-)

> + I have also noticed that some code in tomcat (eg default servlet) has been
>   written so that it will support either approach - hence I had thought
>   they were getting ready to change?

I believe that they wrote their default servlet in this way only to allow
"both" ways... So that you can use the "DefaultServlet" both if mapped to
"/" or to "/....whateverelse.../..."...

It's a hack! :-)

> But I guess they are all just lame excuses...  so it is probably time to
> change or at least add optional behaviour.

Dunno, but if you do and you change the default servlet, then make sure that
it can work both ways (so that one can re-use the default servlet to serve
some content also when it's not mapped to "/").

> Do you need this urgently or can you work around it for now?

I don't think it's that urgent, it's up to the Cocoon folks to tell me if
they want it ASAP or they can wait...

But as I told you, I can throw some hours in if it needs fixing.

I believe though, that although we fix that in Jetty, it will need to be
fixed in Cocoon as well, because if someone decides to map "Cocoon" to
something else than "/" (like, let's say "/*.xml" -> Cocoon folks don't
flame me I know it's just a silly example), that change in the mapping would
bring the problem back as well...

Y'all... Should we do a double fix to both Cocoon and Jetty at the same


To unsubscribe, e-mail:
For additional commands, email:

View raw message