On Sun, 9 Sep 2001, Andrew wrote:
> Date: Sun, 9 Sep 2001 12:14:33 +0400
> From: Andrew <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: Mapping question- suggestion
>
> First, thanks to All for fast respond. And I've read spec and know that
> this not possible but I was believe Tomcat provide some "extension" for
> such cases.Some little notice: Microsoft products(XML support in .NET for
> example) doesn't use specs as is but add a litle bit more functionality for
> user's convience.I think it's a goot practice as it allow correct tiny(not
> visible maybe) spec gaps "on the fly".I suppose Microsoft as one of main
> participants in specs development
> declare only "form/sructure" elements while hide some useful extensions for
> use in their own products. So, one could not be afraid to look "beyond"
> spec.
> Let's be more inventive.
There's a different that is at least as compelling in the Java community
-- let's be portable.
This is specifically not an issue that Microsoft does not need to address,
because they only need to be compatible with themselves (which is why they
don't need specs - whatever the product does is what the standard is, and
it can change at any time). But, there are > 25 licensed J2EE platforms
(all of which support servlet 2.2), plus a bunch more non-J2EE servers
that are also compatible with the specs (including Tomcat). And web
applications that conform to the specs run on *all* of them.
Let's say Tomcat was modified to be non-portable in this regard.
Naturally, you'd want to go ahead and use this feature. But, the moment
you do, you are locked in to Tomcat now and forever more. Is that what
you really want?
No, I didn't think so.
And if you really do, well, that's why the source is there for you to lock
yourself in. The main class you will need to mess with is
org.apache.catalina.core.StandardContextMapper, but there are some other
places that will be affected also.
Craig
