Talk:Jakarta Servlet

Broken Example

The example contains synchronized (sharedCounter) using the object that it is replacing with sharedCounter++. This is the worst thing a programmer can do. sharedCounter is read before the synchronized block is entered, without any thread safe construct, leading to an unpredictable result, followed by synchronizing on that unpredictable result. Synchronization can only work when it is using the same object each time.

178.6.225.132 (talk) 07:16, 5 May 2021 (UTC)

Servlet API versions

Maybe you should specify which Servlet API versions are supported by each servlet container.

How can i use genricservlet for FTP or ny other protocol please discribe through simple examples?????

Try this forum: https://java-net.dev.java.net/servlets/ForumMessageList?forumID=92

Do you think this is a bit too jargon-heavy for lay readers such as myself, rather than those with prior experience of such matters? 194.73.118.78 13:57, 1 August 2006 (UTC)

• I agree, I think its got a little too much Sun Hype/Biz Speak in it, I'd like to see it in more down to earth web-server'ish terms if possible. 218.214.138.11 06:37, 21 February 2007 (UTC)

PHP

Is it correct to put PHP in a list with CGI and ASP? PHP scripts may be invoked in CGI, but, generally, PHP is a language, not a technology or something like that... or am I wrong?--VictorAnyakin 08:14, 4 July 2006 (UTC)

PHP is CGI, but it can be embedded in HTML, instead of the "echoing" of "normal" CGI. It is really only cosmetics for humans, you know. :)

• Sorry but that's completely incorrect. PHP is an independant subsystem, exactly like jsp (and considerably easier to use in my opinion). I find its clumping with CGI a bit jarring, and its peering with ASP very jarring - ASP only works on one platform (actually not true, some maniacs backported it into Apache, nobody knows why), PHP - and don't forget mod_python ! - works pretty much on everything.

218.214.138.11 06:37, 21 February 2007 (UTC)

Yes i too think servlets are useless in this world.. —Preceding unsigned comment added by 210.212.192.18 (talk) 02:50, 7 October 2008 (UTC)

Missing References

There isn't a single reference for this article. Could someone please help out with this? I imagine much of the information in this article can be gleaned from the Sun specification and documentation docs under the product page for java servlet technology--weezology (talk) 00:31, 14 October 2009 (UTC)

Equivalence of CGI and ASP.NET

Non-Java dynamic content. That's not to say non-dynamic content. It's just that Java is the exclusive property of Sun. Microsoft offered Java for a while until they were overwhelmed with a desire to modify the Java standard, thereby violating their contract with Sun. Hence, Microsoft offers little in the way of Java. --173.66.64.90 (talk) 18:12, 21 February 2010 (UTC)

What is "A Servlet"?

The article uses the word servlet in capitalised form. Is this a short form for "Java Servlet"? I think that it should not be capitalised at all, as you can see here. Sae1962 (talk) 14:40, 26 April 2011 (UTC)

JSP container?

JSP container redirects to this article. Why? What is it? --Abdull (talk) 19:11, 26 June 2011 (UTC)

Changed. Now JSP container redirects to JavaServer Pages. 77.6.237.100 (talk) 15:36, 11 May 2012 (UTC)

"Java Servlet" or "Java servlet"?

Shouldn't it be "Java servlet" instead of "Java Servlet"? --Mortense (talk) 13:11, 2 February 2014 (UTC)

No. [1] Nor are they "a sort of Applet" Andy Dingley (talk) 20:06, 2 February 2014 (UTC)

Why is there a diagram of a JSP file lifetime?

What's JSP and why is there a diagram of its lifetime in the intro? — Preceding unsigned comment added by 193.13.114.130 (talk) 18:42, 13 February 2014 (UTC)

The Diagram is still incorrect. The second phase/run of a JSPs life cycle starts at the .Class file, and no where else. That's just basic java. No exceptions. — Preceding unsigned comment added by Davidvsop (talk • contribs) 17:14, 15 October 2014 (UTC)

This article is not about the Java class

The question of upper/lower case usage is recurrent on this page but does not seem to have been clearly addressed. The lower-case term, "servlet", is more prevalent in the literature and refers to the servlet concept (e.g.[2]) whereas, the upper-case term, "Servlet", is used to refer to the Java class (technically an interface). It's clear to me from the content that the article is not about the class but the concept (with appropriate references to the class). If that is the consensus here, then I propose we change the article title to "Java servlet". Jojalozzo 17:24, 28 November 2014 (UTC)

Citations

This article seems to have been flagged for incorrect citations. Is it against policy to link to documentation pages online? Should the docs be added as a reference? It would make sense, but a second opinion would help. ThinkBack (talk) 19:03, 14 April 2019 (UTC)

Requested move

The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review. No further edits should be made to this section.

The result of the move request was: Moved. ErikHaugen (talk | contribs) 17:18, 23 December 2014 (UTC)

---

Java Servlet → Java servlet – The upper case form is rarely used to refer to the concept of a Java servlet. The upper case form is almost always used when referring to the Java class. This article is about the concept of a Java servlet (e.g.[3]) and only tangentially about the Java class. Here are the Google Ngram results showing the overwhelming prevalence in book literature of the lower case form over the upper case form. --Relisted. Dekimasuよ! 22:31, 18 December 2014 (UTC) Jojalozzo 01:46, 8 December 2014 (UTC)

• This issue seems to have been broached before by @Mortense: and @Andy Dingley:. Let's see what they have to say about it. bd2412 T 17:28, 10 December 2014 (UTC)

Support – the meaning intended in the title is the generic, as in the lead. Dicklyon (talk) 06:50, 16 December 2014 (UTC)

---

The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.