Return-Path: Delivered-To: apmail-jakarta-taglibs-user-archive@apache.org Received: (qmail 45768 invoked from network); 4 Feb 2003 17:13:55 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 4 Feb 2003 17:13:55 -0000 Received: (qmail 5903 invoked by uid 97); 4 Feb 2003 17:15:23 -0000 Delivered-To: qmlist-jakarta-archive-taglibs-user@nagoya.betaversion.org Received: (qmail 5896 invoked from network); 4 Feb 2003 17:15:22 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 4 Feb 2003 17:15:22 -0000 Received: (qmail 35919 invoked by uid 500); 4 Feb 2003 17:11:14 -0000 Mailing-List: contact taglibs-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tag Libraries Users List" Reply-To: "Tag Libraries Users List" Delivered-To: mailing list taglibs-user@jakarta.apache.org Received: (qmail 35870 invoked from network); 4 Feb 2003 17:11:13 -0000 Received: from umbongo.flamefew.net (64.253.103.114) by daedalus.apache.org with SMTP; 4 Feb 2003 17:11:13 -0000 Received: by umbongo.flamefew.net (Postfix on Linux (i386), from userid 500) id 8E55D3A2482; Tue, 4 Feb 2003 12:11:15 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by umbongo.flamefew.net (Postfix on Linux (i386)) with ESMTP id 8D3AF296D7A for ; Tue, 4 Feb 2003 12:11:15 -0500 (EST) Date: Tue, 4 Feb 2003 12:11:15 -0500 (EST) From: Henri Yandell X-X-Sender: To: Tag Libraries Users List Subject: RE: Non Java Developers, programmers using JSTL and taglibs In-Reply-To: <513F1D9DFA0CD311BC5B0008C773DC5F034531D8@moscow.sri.srg-ssr.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tue, 4 Feb 2003 Eric.Lewis@swissinfo.ch wrote: > I disagree... By using a scriptfree TLD (as described in "JSTL In Action"), > you can very well restrict your web designers to use only JSTL (or whatever > tags you want them to use). Our web designers aren't allow to publish any > JSP pages unless the first line reads > <%@ taglib prefix="scriptfree" uri="/WEB-INF/scriptfree.tld" %> Sadly I don't get to work with web designers, but this sounds like the way to go. The problem I found in the past with web designers is two-fold. #1 Our Java screws up their tools. JSTL solves this. #2 They can't get their heads around if/loop constructs and variable management. This they'll never do, it's the foundation of being a programmer. In addition, working with PHP designers, they do quite happily understand how to output a variable, if it is there. If working with web designers in JSP, I would define a sub-set of JSTL to teach to them first. How to output variables, maybe how to modify a date-format etc. As Eric has done, I would ban Java code in the page, but reserve the right to insert it myself. I would also teach them the concepts of including, along with the jstl tag for includes. Designers love including once it's beaten into them [joke. ish. honest. ]. > Also, we haven't used anything but JSTL up to now (ok, except for the String > Tag Library, which is handy...). Frankly, I don't see the point in creating > custom tags yourself at all. JSTL doesn't have everything yet :) Also it can be nice to define tags with business-level naming. Then teach these to your designers. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: taglibs-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: taglibs-user-help@jakarta.apache.org