|
You do not want any HTML in a servlet
Monday was the first day of the second annual O'Reilly Conference on Enterprise Java. I'm filling in for Bob Eckstein, who had a string of bad luck, including a long wait in the Phoenix airport, a flying piece of metal that got stuck in his eye, and a speaker who couldn't get to the show. (Bob -- with that piece of metal in his eye -- covered for the speaker.)
|
|
Enterprise Java
JSPs or Servlets--Which Architecture is Right for You?
SINCE THE INTRODUCTION of JSP technology, two architectures have emerged for building server-side Web applications in Java. The first involves JSPs only, and the second uses JSPs and Servlets together. Referred to as Model 1 and Model 2 architectures, respectively, each model has its advantages and disadvantages. The Model 2 architecture has become quite popular recently, and has received a great deal of coverage on the Web and in trade magazines. In fact, many developers mistakenly believe this architecture has replaced the Model 1 architecture and is the "right" way to use JSPs.
|
|
PHP, Perl, Java servlets -- Which one's right for you?
Still can't decide whether to use PHP scripts, Perl CGIs, or Java servlets for your next Web development project? This article will help you decide by providing a side-by-side comparison of the functioning source code of all three languages. The three simple example programs provided take you from the most basic server-side scripts through object orientation to a simple Web storefront presenting product information to a user.
|
|
Web Applications as Java Servlets: Just say no to JSP
The conventional approach to building web-based applications involves writing the user interface components of the application in HTML-based languages such as Sun's Java Server Pages (JSP) or Microsoft's Active Server Pages (ASP). In this article, I'll describe a different approach — one that exploits Java's type-checking ability to validate field parameters and detect invalid links between pages
|
|
Take control of the servlet environment, Part 1
The ever-popular servlet cleanly and simply develops and deploys Web-based applications. However, although Java is platform independent, the Web as a whole is not. The language and the servlet API do not provide such niceties as optional session-persistence schemas (i.e., store in memory, in a database, or in a cookie), and they don't easily accommodate ad hoc solutions to shortcomings in cookie handling.
|
|
Powering the Web Experience with Dynamic Content
technology has done much towards making Web application development an easier task. With a platform- and server-independent approach based on the JavaTM language, servlets provide developers with an easier way to build high-performance, dynamic Web pages compared to traditional CGI programs.
|
|
Untangle your servlet code with reflection
You can enlist the Reflection API to unravel an all-too-common problem in servlet development: doGet() and doPost() methods that grow long, complex, and hard to extend and debug. The use of reflection described here is fairly lightweight, requires minimal code, demands little developer commitment, and should integrate well with other development techniques used in your team.
|
|
Solve your servlet-based presentation problems
Should you use raw servlets, JSP pages, servlets with a templating engine, an automatic HTML-to-Java compiler, or XSL stylesheets to implement content presentation in your next thin-client application?
|
|
Pushlets: Send events from servlets to DHTML client browsers
Server-side callback through RMI or CORBA can notify clients of changes in the server such as those needed to keep the clients' GUIs up-to-date with the state of the server application. But what if the client is a Web browser whose page content needs to be updated? In this article Just van den Broecke explores pushlets, a servlet-based notification mechanism that enables server-side Java objects to call back JavaScript code within a client browser
|
|
Enterprise Java
Large-Scale Servlet Programming
THE JAVA SERVLET API and Java Server Pages (JSPs) are a great help in developing high-performance, server-side Java programs for the Web. However, there are considerations that have to be taken into account when dealing with very large, high-traffic Web sites that can affect the design of your servlets. We examine the key scalability issue of storing client data on the server and some approaches for making your servlets perform in a high-traffic environment.
|
|
Poll results: Developers sound off on servlets
ervlets have been getting a lot of press lately (including the two cover stories in this month's JavaWorld). But how are developers really using servlets, and why are they employing servlets instead of some other technology?
|
|
Architecture of the Servlet Package
Servlets are Java technology's answer to CGI programming. They are programs that run on a Web server and build Web pages.
|
|
Trail: Servlets: Table of Contents
Servlets are modules that extend request/response-oriented servers, such as Java-enabled web servers. For example, a servlet might be responsible for taking data in an HTML order-entry form and applying the business logic used to update a company's order database.
|
|
Sending rich messages between client and server using asynchronous messaging
Erik's previous article, "Remote scripting using a servlet," described an infrastructure for asynchronous remote scripting between a browser and a servlet backend. This article expands on that premise by describing an asynchronous messaging system that allows rich messages to be sent back and forth between client and server. In order for these messages to be compliant with most browsers, they will be sent as JavaScript objects. This article builds on the code presented in the earlier piece, and creates an automated messaging layer so that the browser and server can keep in constant contact with one another.
|
|
Java Servlets: Design Issues
In the web-application server domain, Java servlets are fast replacing the CGI. By year 2000, most of the Java based application servers are expected to be based on Java servlets for connecting the middle-tier components with the HTML content (or templates).
|
|
Java Servlets and Java Server pages Code Camp
If you are an ISV development engineer, then Sun Code Camps are an ideal place to gain hands-on experience with Sun's new technologies. Code Camps are packed with technical content, hands-on programming exercises and sample code. Sun's Code Camp leader provides an engineer-to-engineer learning experience that is intensive and technically stimulating. The focus is on delivering programming information and sample code that you can put to good use right away.
|
|
Java Servlets versus CGI -- Implications for Remote Data Analysis
The Common Gateway Interface (CGI) was the first attempt to enable the creation of dynamic HTML pages which represent a very suitable concept to meet the requirements of web-based applications for remote data analysis (RDA). CGI scripts are still popular, but by now there are new approaches which should be able to solve the main CGI problems. In this paper, we present the most promising one: Java Servlets. We will discuss the advantages and drawbacks of Java Servlets compared to CGI scripts. Moreover, we will do some performance measurements on the basis of simple classification problems and introduce the key functions of the Java Servlet API. 1 Motivation Remote data analysis could be
|