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
- List Job (QUSLJOB) API
- Using QCLRDTAQ to clear data queues in CL and RPG
- What is QZHQSSRV job?
- Make a Home made, open source mp3 Player
- 80 Column Punched Cards and the History of RPG on the AS400
- UDATE and *DATE in AS400 RPG
- API Example - Deleting Old Spooled Files
- AS400 APIs
- QUSRJOBI API (Retrieve Job Information) as400
- Creating an as400 Query
No comments:
Post a Comment