JavaServer Page

Summary type=”email”/> < %-- snip Starting with this point we are back to the previous JSP file snip --%> b Asserting a single parameter based on its type, the existence assertion is implicit. Asserting on a named parameter became a very simple matter. We actually reduced many potential scriptlets (to validate parameters) and made our page more robust. Our AssertTag may not be the Holy Grail (we cannot pose really complex questions on the parameters) but it is extensible. However, even with the relatively limited functionality that we have, assertions can solve most problems we confront in our daily work. 7.6 Summary Tags have clearly facilitated sending emails with dynamically generated content from within a JSP. We have gone from something that usually requires in-depth know-how, such as SMTP and Java mail, and rendered its power in such a pervasive way that any page author comfortable with tags can use it. The key issue was not the underlying email technology, but how to create a simple, robust interface to that technology with custom tags. The role of custom tags is not to develop a new technology, but to enable rapid development and to expose a wanted technology in the most convenient, pervasive way to your JSP developers. Is there a drawback to the tag approach? Perhaps. A Java developer may look at the tags and believe that they are less easy to use than JavaBeans. He or she may say, Hey, I put all that effort into the tag and all I got is functionality that I could have implemented with a couple of scriptlets and a simple email bean . This may be true, yet that effort freed us from the need to maintain all the scriptlets involved in JavaBeans usage, and helped further separate the duties of Java coders from the JSP page authors.

Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Java Web Hosting services