Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Delivered-To: moderator for tomcat-dev@jakarta.apache.org Received: (qmail 46624 invoked from network); 20 Jun 2000 02:23:56 -0000 Received: from smtp.screaming.net (212.49.224.20) by locus.apache.org with SMTP; 20 Jun 2000 02:23:56 -0000 Received: from negrito (dyn136-ras35.screaming.net [212.188.130.136]) by smtp.screaming.net (8.9.3/8.9.3) with SMTP id CAA02817; Tue, 20 Jun 2000 02:25:49 GMT Message-ID: <00ad01bfda2e$e5a4d940$8882bcd4@negrito> From: "Juan Jose Pablos" To: , "Arieh Markel" References: <200006191835.MAA24392@durango.Central.Sun.COM> Subject: Re: Localization and DefaultServlet Date: Mon, 19 Jun 2000 21:38:52 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Ariel, > The problem with appending the is such that in Unix systems, due > to not having a 'filetype' component as an integral part of a pathname, > it would force to make too many assumptions on where the insertion of the > should happen. I think you need to define the extension in other to be recognize by tomcat, appending the locale force the same assumtions of using the extsion to define the Mime type. do not you use web.xml to define the Mime-mapping in Unix? If I remove the .jsp or the .class, Jsp and servlets won't work, I think that Mac is diferent but I am not a Mac fan. > I don't want to do it in such a manner. > It is not the way we already do it for the servlets/JSP?, it is possible to check how other servlet engine take this problem, maybe there is already a Standar so if my War file work with language content negotiation in Tomcat, it could work with other servlet engine. > So far, I am thinking of changing the locale at the root of the document > hierarchy (/en/a/b/c/d) - assuming docRoot is '/' in this example, which will > make the search/identification of an existing document simpler, as the docBase > needs to be prefaced with the locale. > > If in a different context, for example where the docRoot would be > /services, then /services/dir1/dir2/file.html would be searched first > as /services//dir1/dir2/file.html. Ok, Make sense, but it means that we can not create any directory that mach with a especific locale in the document Root or in the Context root isn't it? if you create a service/en folder, for Electronict nany (en), a spanish person could see the /services without problems, for a english person the server will display the contents of the /service/en instead of /services, the server assume that /en is the language instead of a dummy directory. (Maybe we can live with that anyway...) > Like I said before, it introduces some problems as far as the naming of the > resource and assuming that there is indeed a filetype. Imagine for > example that a pathname has no filetype, i.e. /a/b/my_image, > in such a case the would be appended and not inserted prior to > the (last - in this case inexistent) period. I am not sure about this but your Image could not be display if you do not add the extension anyway , Servlets and JSP need the extesion in order to work. In the matter that a file has not got the language extension then you assume that has got the default language for the context. De nada, Juan