Talk:Jakarta Server Pages

message: Perhaps a comparison of ASP vs. JSP vs. PHP? —The preceding unsigned comment was added by 70.101.158.1 (talk) 04:07, 19 December 2006 (UTC)
thread_title:  Comparison? 

message: Didn't this page used to have a criticisms section, whereas it cited problems with Java twisted to a web development platform
Tolland (talk) 19:58, 8 August 2022 (UTC)
thread_title:  Criticism 

message: I agree that this page could use a comparison section as well as a criticism section. As a Java web developer I am all too aware of the failings of developing directly using Java/JSP/JSTL/Servlets without additional technologies to ease the pain.  —Preceding unsigned comment added by 64.201.43.121 (talk) 14:24, 3 June 2008 (UTC)
thread_title:  Criticism and Comparison Sections Needed 

message: The section about jsp:plugin seems to violate NPOV.  There is alot of "hopefully" and 'X is poorly done.'  Someone should revise this.
:I did some work on that, but it could maybe use another look. AdjectiveAnimal 15:25, 5 July 2007 (UTC)
thread_title:  jsp:plugin section 

message: The article looks like a good introduction to JSP technology for people already familiar with Java Servlet technology. I like code examples and short programmer's reference in Wikipedia. Both of nontechnical users and developers should be satisfied.  —Preceding unsigned comment added by Vi2 (talk • contribs) 17:06, 27 April 2008 (UTC)
thread_title:  Good introduction to technology 

message: This article is really not what I would expect at all. It has no history, or pedigree for the JSP (where does it fit in with PHP, ASP, etc?), at all, and basically acts a beginners guide. For people wanting to know the why, what and where of JSP this article doesn't really seem to answer it.
Jimadilo (talk) 23:18, 22 December 2008 (UTC)
replies: text: I have refactored the article to transform it to an encyclopedic article and I have moved the tutorial information there. Ftiercel (talk) 13:15, 18 September 2009 (UTC)
thread_title:  Developer not satisfied 

message: # "This system of split inline coding sections is called step over scripting because it can wrap around the static markup by stepping over it." - I have never heard of this term, and the only place google can find it is in copies of this article.
# I don't like the whole description of 'runtime' compilation. That's exactly the opposite of what happens. JSPs are compiled into Servlets which are executed at runtime, possibly including output from other compiled JSPs. That's why you can pre-compile all your JSPs.
# I have a problem with the term JSP pages and I think it should be JSPs as a replacement.
# The JSP and compiled Java code in the example do not help or make anything clear, I think they should go, and be replaced with some simple examples of JSP syntax only, maybe with a description of the output. The Java generated is unimportant.
— M3TA(info) @ 09:50, 3 March 2010 (UTC)
thread_title:  Errors 

message: I'll be editing this article to have a better organizational structure, and I'll be removing some unnecessary/technical text as well as adding some information for people who are unfamiliar with Java servlets (and might be more familiar with PHP.)
I'd like to add a criticism section, as well as a section with basic comparisons to PHP or ASP.NET for people who might be familiar with those technologies. If you have sources I could use for the criticism section, that would be helpful. --Libertyernie2 (talk) 16:17, 12 April 2012 (UTC)
replies: text: Add encyclopedic content on this page and tutorial content on this one. Ftiercel (talk) 07:29, 13 April 2012 (UTC)

text: You've done a great job with this rewrite. The outline is logical, the examples are concise and are good representations of what JSP actually looks like. The comparison section is especially good. The compiler section could probably use a couple of sources, and you may want to think about adding in an example using JSTL.The only other criticisms I would have are some minor edit things; minor grammar fixes etc. Nice work. Ben.d.zimmer (talk) 16:33, 26 April 2012 (UTC)
thread_title:  Work in progress 

message: The caching section in this article is roughly more about general web application scalability than it is about JSP caching.  I'm not sure if it's still relevant, but O'Reilly has a page on it.  And even if this were talking about a general Java web application, the content in this section is also refutable.  — Preceding unsigned comment added by 111.94.212.83 (talk) 11:54, 29 November 2012 (UTC)
replies: text: Yup. The "bottleneck" described has nothing to do with JSP or servlets, you got that with PHP or whatever else, too. I like the caching section, but it needs to be described more generally. The database is always the bottleneck, unless you're using a very fast "noSQL" database and a slow Apache server. 178.197.233.41 (talk) 12:04, 22 May 2013 (UTC)
replies: text: Agreed. I've read through the section and it does seem a dubious one. There's certainly a space for improvements & citations there.Vaxquis (talk) 10:58, 9 June 2013 (UTC)
thread_title:  Misleading caching section 

message: Hello fellow Wikipedians,
I have just modified  on JavaServer Pages. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive http://web.archive.org/web/20120419215245/http://java.sun.com:80/products/jsp/tutorial/TagLibraries3.html to http://java.sun.com/products/jsp/tutorial/TagLibraries3.html#63159
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).
Cheers.—cyberbot IITalk to my owner:Online 17:58, 24 June 2016 (UTC)
thread_title:  External links modified