I agree with the points made in this thread that the STL standard is itself useful documentation, that there are other great free resources available in support of JSTL usage, and that the documentation distributed with the STL could be improved. Nonetheless, sometimes it makes sense to buy a resource that will make a difference. If you're going to be using JSTL more than a little bit, it's a great book to have skimmed once, keep around for reference, and be able to hand to others who need to understand your JSTL usages.
Andrew
Full disclosure: I know Shawn outside the context of JSTL.
Yes. Thanks to both of you for pointing that link out. I've already downloaded and looked at the pdf (it fixed the problem I was having).Well, there's the spec itself, which is actually very readable.
There's also the (freely available) Appendix A from Shawn Bayern's "JSTL In Action", which is what I tend to use:
http://www.manning.com/bayern
The full link to Shawn's reference can be found at:
http://www.manning-source.com/books/bayern/bayern_apxA.pdf
It's also worth mentioning that when you download standard taglibs you getHmm...Do you mean standard-taglibs.jar? I've extracted and have run standard-doc.war which has two html pages that basically point elsewhere...
a standard-taglibs.war file which can be deployed in Tomcat and contains
not only a reference but also example code.
I wish that all of the jakarta taglibs examples could be be bundled into aWell, I still would like to see taglib documentation distributed with the standard-taglibs. I really appreciate the help I've gotten from the list, but I am disappointed that the result has been links to external references and the specification. Even before I joined the list, I spent some time googling, searching on java.sun.com for information on what the available tags in jstl were, etc...Maybe I'm coming at this from the wrong direction, I've been working with Java for a number of years and to me it just seems natural that if you have an API you would have a set of HTML files (Javadoc) describing that API. In this case, I was expecting/looking for something similar to http://jakarta.apache.org/taglibs/doc/application-doc/index.html
single context so that all of the taglib examples could be deployed one
time instead of having multiple contexts.
I just found it frustrating that the resources that I am used to aren't available.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
