Warning: file_put_contents(/opt/frankenphp/design.onmedianet.com/storage/proxy/cache/27875a5a3d2a664c600f4d6f6a337602.html): Failed to open stream: No space left on device in /opt/frankenphp/design.onmedianet.com/app/src/Arsae/CacheManager.php on line 36

Warning: http_response_code(): Cannot set response code - headers already sent (output started at /opt/frankenphp/design.onmedianet.com/app/src/Arsae/CacheManager.php:36) in /opt/frankenphp/design.onmedianet.com/app/src/Models/Response.php on line 17

Warning: Cannot modify header information - headers already sent by (output started at /opt/frankenphp/design.onmedianet.com/app/src/Arsae/CacheManager.php:36) in /opt/frankenphp/design.onmedianet.com/app/src/Models/Response.php on line 20
The Java Community Process(SM) Program - JSRs: Java Specification Requests - detail JSR# 53
Find JSRs
Submit this Search


Use of JCP site is subject to the JCP Terms of Use and the Oracle Privacy Policy
JCP Info
  • About JCP
  • Get Involved
  • Community Resources
  • Community News
  • FAQ
  • Contact Us
  • Ad Banner
     
     
     
     

    Summary  |  Proposal  |  Detail (Summary & Proposal)
    JSRs: Java Specification Requests
    JSR 53: JavaTM Servlet 2.3 and JavaServer PagesTM 1.2 Specifications

    Stage Access Start Finish
    Maintenance Draft Review 2 Download page 24 May, 2002 24 Jun, 2002
    Maintenance Draft Review Download page 22 Mar, 2002 22 Apr, 2002
    Final Release Download page 25 Sep, 2001  
    Final Approval Ballot View results 21 Aug, 2001 04 Sep, 2001
    Proposed Final Draft Download page 26 Sep, 2000  
    Public Review Download page 16 Aug, 2000 15 Sep, 2000
    Participant Review Login page 05 Jun, 2000 05 Jul, 2000
    CAFE   08 Feb, 2000 22 Feb, 2000
    JSR Approval   01 Feb, 2000 07 Feb, 2000
    Status: Maintenance
    JCP version in use: 2.1
    Java Specification Participation Agreement version in use: 1.0


    Description:
    The next versions of the JavaTM Servlet and JavaServer PagesTM (JSP) specifications.

    Please direct comments on this JSR to the Spec Lead(s)
    Team

    Specification Leads
      Eduardo Pelegri-Llopart Sun Microsystems, Inc.
    Expert Group
      Adobe Systems Inc. America Online (AOL) Apache Software Foundation
      Apple Computer, Inc. Art Technology Group Inc.(ATG) Avedal, Karl
      BEA Systems Bergsten, Hans Borland Software Corporation
      Developmentor Ferrier, Nic Fujitsu Limited
      Gemstone Systems, Inc. Hewlett-Packard Hunter, Jason
      IBM Intalio, Inc. InterX PLC
      jGuru.com Lutris Technologies Macromedia, Inc.
      New Atlanta Communications, LLC Oracle Persistence Software Inc.
      Rydin, Magnus SAS Institute Inc. Silverstream Software
      Sun Microsystems, Inc. Sybase WebGain

    Original Java Specification Request (JSR)

    Identification | Request | Contributions

    Section 1: Identification

    
    Submitting Participant:
    
    Eduardo Pelegri-Llopart and Danny Coward
    Java Software, Sun Microsystems, Inc. 
    901 San Antonio Rd, MS UCUP02-201, Palo Alto, CA 94303 
    
    Phone: +1 408 343 1456 and +1 408 343 3551
    Email:
           Eduardo.Pelegrillopart@eng.sun.com
           Danny.Coward@eng.sun.com
    
    

    Other Participants Endorsing this JSR

    Most partners that participated in the definitions of Servlet 2.2 and JSP 1.1 specifications have already expressed interest in participating in the expert group for Servlet 2.3 and JSP 1.2. Partners that are endorsing this JSR include:

    Frank Biederich
    Adobe
    Simeon Simeonov
    Allaire
    Joe Chung
    ATG
    Dave Brown
    BEA
    Bob Bickel
    Bluestone Software
    Scott Ferguson
    Caucho
    Assaf Arkin
    Exoffice
    Craig R. McClanahan
    ASF & Jakarta
    Elias Bayeh
    IBM
    Hans Bergsten
    Gefion Software
    Ethan Henry
    KL Group
    Jason Hunter
    Author of "Java Servlet Programming"
    Amit Kishnani
    Macromedia
    Stefano Mazzocchi
    ASF & Cocoon
    Todd Giles
    Net Objects
    Bjorn Carlson
    Netscape
    Vince Bonfanti
    New Atlanta
    Julie Basu &
    Hal Hildebrand
    Oracle Corp.
    Tim Lopez
    Visual Cafe Group (WB Information Systems)
    Magnus Stenman
    Orion App Server
    Jon Stevens
    ASF, Turbine &
    Clear Ink Corp.
    Arny Epstein
    SilverStream
    Larry Cable
    Sun Microsystems

    Section 2: Request

    This JSR requests the creation of the next versions of the Java Servlet and JavaServer Pages specifications. The version numbers tentatively assigned are Servlet 2.3 and JSP 1.2. These two specifications will be part of the Java 2 Enterprise Edition platform.

    Since the JavaServer Pages specifications are tightly defined on top of the Java Servlet specifications, we plan to define both specifications in parallel to eliminate discrepancies and confusion, and to reduce development cost. We plan to structure the documentation so that the Java Servlet specification can be used independently of the JavaServer Pages specification,

    2.1 Target Java platform

    The Servlet 2.2 and JSP 1.1 specifications are part of the Java 2 Enterprise Edition, version 1.2 (J2EE 1.2) platform. We expect that this proposed specifications will be part of the next release of the J2EE Platform. As with the current versions of the specification, we expect the new versions to be usable on the J2SE platform.

    2.2 Need of the Java Community that this work addresses

    The new Servlet and JSP specifications will add some functionality that was already known to be missing from the current specifications and that was not incorporated due to time constraints or because additional research was needed before determining the correct approach.

    In addition, the new Servlet and JSP specifications will incorporate new functionality requested by our parterns and the public, reflecting, in some cases, their quickly evolving needs.

    The requirement areas we intend to address include, but are not limited to, the following:

    • Better support for localization of applications
    • Proper support for inclusion of JSP pages without forcing flushing of buffers
    • Support for application events
    • Improved debugging and other tool support, taking advantage of JSR-45
    • Improved XML support
    • Improved tag library support
    • Improved JSP authoring support
    • Better support for composition of components
    • Enabling of WebDAV and WAP requests

    In some cases the same solution may address multiple requirements. Also, in some cases, the best response to the requirement may be outside of the specification.



    2.3 Explanation of why the need isn't met by existing specifications

    As discussed above, these areas are largely unspecified in Servlet 2.2 and JSP 1.1. Consequently, Web Application authors, server vendors and tool vendors must either ignore these areas or offer support using vendor-specific architectures.

    2.4 Specification to be developed and how it addresses the need

    We request the development of a new version of the Servlet specification and a companion new version of the JavaServer Pages specification.

    2.5 Detailed description of the underlying technology or technologies

    A detailed description of Servlet 2.2 and JSP 1.1 functionality can be found in the respective specification documents, which can be downloaded from the sites at http://java.sun.com/product/servlet/download.html and http://java.sun.com/product/jsp/download.html.

    2.6 Proposed package name for API Specification

    We expect to use the existing packages used by the Servlet 2.2 and JSP 1.1 specifications: javax.servlet, javax.servlet.jsp, and javax.servlet.jsp.tagext.

    2.7 Security implications

    Security mechanisms must be compatible with the security facilities of J2SE 1.3.

    2.8 Internationalization implications

    Improved internationalization and locatization capabilities for JSP and Servlets is one of the key goals of this JSR, as noted above.

    2.9 Localization implications

    See 2.8.

    2.10 Risk assessment (impact of work on target platform, impact if work not carried out, difficulties in carrying out RI and/or CTS)

    In the absence of these new specifications, it is highly likely that Web containers providers will develop container-specific mechanisms to support the facilities listed in section 2.2 of this document. If this occurs it will limit the portability of Servlet and JSP applications and tools.

    An analysis of partner needs must be done to determine whether it is possible to target the new specifications exclusively to the Java 2 platform, or if the earlier versions of the specification still need to be considered.

    2.11 Existing specifications that might be rendered obsolete or deprecated by this work

    A primary goal is backward compatibility. All applications that use the Servlet 2.2 and JSP 1.2 specifications must be compatible with Servlet 2.3 and JSP 1.2 specifications.

    2.12 Existing specifications that might need revisions as a result of this work

    See 2.11 above.

    Section 3: Contributions

    3.1 List of relevant existing documents:

    JavaServer Pages Specification, Version 1.1
    http://java.sun.com/products/jsp

    Java Servlet Specification, Version 2.2
    http://java.sun.com/products/servlet

    Java 2 Platform, Enterprise Edition Specification Version 1.2
    http://java.sun.com/ j2ee/docs.html

    The Java 2 Platform, Enterprise Edition Application Programming Model
    http://java.sun.com/j2ee/apm

    JSR-039, "Java Servlet and JavaServer Pages Performance"
    http://www.jcp.org/jsr/detail/39.jsp

    JSR-045, "Debugging Support for Other Languages"
    http://www.jcp.org/jsr/detail/45.jsp

    JSR-052, "A Standard Tag Library for JavaServer Pages" (in preparation)
    http://www.jcp.org/jsr/detail/52.jsp



    3.2 Explanation of how these items might be used as a starting point for the work

    These Servlet 2.3 and JSP 1.2 specifications will be based on the current Servlet 2.2 and JSP 1.1 specifications. The Application Programming Model work will be used to ground the new designs. The J2EE documents provide context for the use of Servlets and JSP within the J2EE platform.

    We expect to take advantage of the experience gained from a number of projects, including several that are represented in the endorsement list.

    JSR-052, "A Standard Tag Library for JavaServer Pages" requests the creation of a standard JSP tag library; that specification effort will have a symbiotic relationship with this one. Similarly, we expect to take advantage of JSR-045 "Debugging Support for Other Languages" to provide improved debugging support for JSP. Finally, we expect to start getting some feedback from and input into JSR-039, "Java Servlet and JavaServer Pages Performance".