The following comments have been recorded for No

• 1 (16 Nov 2016 00:00)
• http://carinsurancepu.top/academy-auto-insurance.html http://carinsurancepu.top/auto-insurance-laws-in-va.html http://autoinsurancesm.top/public-liability-insurance-for-carpenters.html http://carinsurancepu.top/freeway-auto-insurance-houston-tx.html http://carinsurancepu.top/car-insurance-for-one-week-under-21.html (26 Jan 2016 00:00)
• no idea (12 Dec 2013 00:00)
• but I want to (13 Dec 2005 00:00)
• No (17 Apr 2002 00:00)
• adsasd (3 Dec 2001 00:00)
• using webmacro and i'm very happy with it (23 Nov 2001 00:00)
• XMLC is better (21 Nov 2001 00:00)
• not yet, but it is coming sometime early next year (20 Nov 2001 00:00)
• I mostly use APSs and haven't looked into JSPs much yet. (20 Nov 2001 00:00)
• But I'd like to someday. (20 Nov 2001 00:00)
• Use straight servlets mainly... if I want data/layout seperation I use XML-XSL transformations (16 Nov 2001 00:00)
• I don't know how to get jsp to work on my apache web server (15 Nov 2001 00:00)
• very good. (14 Nov 2001 00:00)
• I've used JSP alternatives instead. (12 Nov 2001 00:00)
• Velocity...no jsp. (8 Nov 2001 00:00)
• I've used Velocity - it is more elegant solution but I'm wondering if JSP has better performance. (8 Nov 2001 00:00)
• Velocity is much nicer and cleaner jakarta.apache.org/velocity/ (8 Nov 2001 00:00)
• I'm trying to determine whether JSP/Servlets are the right implementation for a new project (vs. sticking with a GUI). Having lots of trouble getting information and examples showing how a heavy-transaction system could be written for web access without sacrificing the users' productivity. I've been digging for two weeks, and still no real answers. Are the event handlers in Servlet 2.3/JSP 1.2 comparable to event handlers in GUIs? (6 Nov 2001 00:00)
• the site does not give me that service (6 Nov 2001 00:00)
• I would like to use servlet + XSLT. (5 Nov 2001 00:00)
• Opted to use a template engine instead (Apache Velocity) based on various articles I've read including some from this site. (5 Nov 2001 00:00)
• JSPs are a waste of HTML. Tea, Freemarker, WebMacro and others are much more attractive solutions (5 Nov 2001 00:00)
• Use WebMacro 0.94 on a production site (5 Nov 2001 00:00)
• don't like jsp because it requires the web(page) developer/designer to learn the syntax of java. it is not a total separation of gui and business logic. i've used xmlc before and like it. xmlc also has some disadvantages, but still prefer it to jsp since it's easier for the web designer. some type of combination of jsp and xmlc would be nice. (5 Nov 2001 00:00)
• Prefer Cocoon framework. (5 Nov 2001 00:00)
• Looking at possibly using it for some stuff. (5 Nov 2001 00:00)
• Don't see the point (especially after reading your book :-) ) (5 Nov 2001 00:00)
• ... but we are evaluating STRUTS for our next project. (5 Nov 2001 00:00)
• WebMacro rocks :) (5 Nov 2001 00:00)
• We dont use JSP because it has the same problem as ASP: mix HTML with the CODE. We work with templates and developed a helper class that does all the "dirty work" : load a combo, load a table, set an option button and many other things. (5 Nov 2001 00:00)
• Servlets with ECS type of framework suits us well, don't like the messy look of much jsp code (5 Nov 2001 00:00)
• However I do believe it's the technology to concentrate on. The fragmentation into dozens of other macro engines is not good even if the technology is cleaner. I'd prefer all the effort going in to imroving JSP to make it a stronger standard. (5 Nov 2001 00:00)
• Used freemarker instead (5 Nov 2001 00:00)
• We used to use JSPs but now we use Velocity. (5 Nov 2001 00:00)