This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Chapter 7. Using Custom Tag Libraries and the JSP Standard Tag Library So why is it called a custom tag library if it's a collection of custom actions? Using formal XML terminology, one or more tags (e.g., an opening tag and a closing tag) represent one element (the combination of the tags and possibly a body), but the word "tag" is commonly used to refer to both tags and elements because it's easier to say and shorter to type. Hence, the representation of a custom action (the functionality) in a JSP page is really called a custom action element. But that's just way too many words for most of us to say over and over again. Replacing element with tag doesn't help much, so we cut it down to the bare bones and use custom tag for both the functional entity and its representation in a page. When the JSP specification was written, no one objected to this sloppy language, so now we're stuck with custom tag libraries containing custom actions. I try to stick to the terms custom action and custom action element in this book, but if I slip, be aware that custom action, custom action element, and custom tag mean the same thing.
Test 094, IBM WID 6.0 cert
SCBCD 1.3 Beta
SCWCD 1.4 Beta
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com