JSP best practices: Pack 'em up!: "Storing your taglibs in a local filesystem is great for in-house development and testing, but it's not a good permanent solution. Custom taglibs should be widely accessible, which means they must be distributed in a standard and secure manner. Brett McLaughlin explains how to JAR your custom taglibs for easier maintenance, distribution, and installation in any JSP-compliant Web container.
So far in this series we've kept our custom taglibs in a local filesystem, where we could easily access and manipulate them. While local access is great for in-house development and testing, it's not a good permanent solution. The whole point of custom taglibs is that they should be widely accessible, which means they must be distributed in a standardized way that also allows for some essential security measures. In this installment of JSP best practices, you'll learn how to package your custom taglibs in a JAR file for safe and easy distribution."
Wednesday, January 26, 2005
Subscribe to:
Post Comments (Atom)
Popular Posts
- as400 Iseries Tips
- Common Gateway Interface (CGI) on the as400 / iSeries
- AS400 Job Scheduler
- Why Crunch Mode (Long Hours) Doesn't Work
- Using as400 QRCVDTAQ api to retrieve a message / entry from a dataqueue
- as400 iSeries NetServer Disabled user profiles
- AS400 APIs
- Configuring Tomcat5 and Apache2 with Virtual Hosts using mod_jk
- Adobe Flex 2.0 Beta
- EclipseZone - Clean Up Warnings with the 'restriction' Suppression Flag
No comments:
Post a Comment