Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 67709 invoked from network); 16 Feb 2000 23:37:16 -0000 Received: from cindy.kollegienet.dk (HELO odense.kollegienet.dk) (qmailr@130.226.80.138) by locus.apache.org with SMTP; 16 Feb 2000 23:37:16 -0000 Received: (qmail 6072 invoked from network); 16 Feb 2000 23:37:10 -0000 Received: from unknown (HELO kaa.hco.kollegie.dk) (root@172.16.8.10) by cindy.kollegienet.dk with SMTP; 16 Feb 2000 23:37:10 -0000 Received: from hco.kollegienet.dk (n1203aa.hco.kollegie.dk [172.16.9.132]) by kaa.hco.kollegie.dk (8.8.7/8.8.7) with ESMTP id AAA29524; Thu, 17 Feb 2000 00:37:09 +0100 Message-ID: <38AB33A7.F0457706@hco.kollegienet.dk> Date: Thu, 17 Feb 2000 00:32:55 +0100 From: Eugen Kuleshov X-Mailer: Mozilla 4.61 [en] (OS/2; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: general@jakarta.apache.org CC: tomcat-dev@jakarta.apache.org Subject: Re: request for comments about Multilinguage JSP References: <38AAFC11.BDA50080@earthlink.net> <38AB26C4.F8CBC134@hco.kollegienet.dk> <38AB2E59.D0BA76DC@exoffice.com> <38AB30B4.9DC959FC@hco.kollegienet.dk> <38AB33AC.A33FEB5B@exoffice.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Assaf Arkin wrote: > My test case is actually a Servlet which contains only the logic and > does not generate a single line of HTML. Everything is done in XSLT, and > it rocks. > > Of course that raises the question, why would one use JSP for? > > Certainly not for presentation. But when JSP gains XML capabilities, you > might find it easier to use existing XML beans from inside an XML page. > Your JSP page will in effect invoke beans, glue them together, maybe do > some code, maybe not. > > You will also need to produce some XML for the portion of the > information that is static. Thats right. But it is not the answer on my question and not solve problem of multilanguage JSP. Other reason for don't use XML/XSLP egine is a speed of request processing. "Classical" JSP produced HTML is faster and eat less resources. JSP complied in first request and then run like other servlets. Eugen Kuleshov.