JSP concise Tutorial: Comparison and summary

JSP, ssjs, and NAS
JSP does not replace or threaten ssjs as a web development platform, and they own their own markets. Although JSP is more powerful and flexible than ssjs, you need to write scripts. Code You must learn Java-at least before a vendor releases a simpler language like JavaScript. At the same time, ssjs still provides a simple and powerful JavaScript language, which is easier to learn than Java and is more flexible in some aspects because it can be loosely typed. Since NAS was noticed, it is certain that JSP cannot replace the powerful functions provided by Nas. JSP is an advanced expression layer technology that can coexist well with the NAS architecture. NAS now uses a unique identification language to build a single table template. This logo language is somewhat "stubborn" and does not allow scripts to be added to pages. This is obviously not as flexible as JSP. In nas4.0, Netscape will introduce JSP as an optional identification language to work with the underlying NAS servlet model to be introduced in nas4.0. In fact, the emergence of JSP is good news for NAS developers.

JSP and XML
JSP has an interesting relationship with XML. On the one hand, you can mix JSP and XML, just like hybrid JSP and HTML, so that jsp can be used to dynamically generate xml pages. In other words, you can use JSP to write the original XML document. JSP provides this function in several special classes, but this is not unique to it. Theoretically, you can use any scripting language, including CGI, ssjs, and ASP, to dynamically generate xml pages, just like the HTML method. The JSP specification clearly states that JSP supports dynamic generation of XML documents, and confirms that this method of generating dynamic content does not violate any XML rules.

On the other hand, JSP pages can be interpreted as XML documents. The JSP Specification defines the labels applicable to XML and the labels not applicable to XML. For example, a script snippet (written in <%... %>) can also be written between the applicable xml tag <JSP: sriptlet> and </jsp: scriptlet>. Obviously, when you manually write JSP code, the previous method is easier than the XML format. However, in IDE (integrated development environment) or other JSP development tools, using XML writing format can easily generate valid JSP pages. For more information about the relationship between JSP and XML, see JSP specifications.

Conclusion
JSP will naturally be followed by a variety of Web developers, because it not only uses labelsProgramSupport also applies to advanced script writers and Java developers. In fact, other vendors except Wangjing have also provided JSP development tools in one way or another. Although Sun has not officially released the jsp1.0 specification (the jsp1.0 specification published at the time of this article is just a draft), IBM, beaweblogic, and livesystems have implemented JSP in their application servers. JSP is an open standard that allows other languages (such as JavaScript) to replace Java, so it will win more extensive support in the industry. As mentioned above, Netscape has announced that nas4.0 will support JSP and assumervlets.

The inherent flexibility of JSP, the support for component-centric programming, and its cross-platform nature make it a perfect complement to the Netscape cross-platform service system. Since NAS itself is a component-centric service system supporting Java, JSP seems to be the most ideal single-layer table technology that matches NAs in future versions. If you have been or are about to become a NAS programmer, I strongly recommend that you download the JSP reference implementation released by Sun and learn it from now on. This tool is not used as a production software product, but you can use it to build and run some simple applications to familiarize yourself with JSP. It also includes some sample programs that will guide you through JSP development together with this article.