In the article, I said you could find a libary of JSP custom tag at http://coldjava.hypermart.net/servlets/,that should have been http://coldjava.hypermart.net/jsp.htm.

Folks, I'm sad to have to report that I've now confirmed that the use of CFIMPORT to call JSP custom tags does NOT work in the Pro edition of CF. It will work in Enterprise, as well as the Trial (which is enterprise) and the Developer Edition (which the Trial becomes after 30 days, reverting to a single-user version).

Folks, here's another update of info I've learned since the article. First, you don't HAVE to place your jar file in the web-inf\lib directory as I (and the docs) had stated. I've found that you can indeed put them in the same directory as your CF template that's calling them, and then just say

CFIMPORT TAGLIB="yourtag.jar"...

That's useful if you work in an environment where you may find th web-inf directory locked down for any reason.

Also, in the preview release candidate, you can now refer to TLD files in the CFIMPORT, and again they can be located either in web-inf\ or in the same dir as your code.

Of course, when I say you can put these in the same dir as your code, I also mean you can put them in some other dir in the web root and use a relative reference to point to it.

/charlie

Folks, just wanted to add some info for you. If you try out these tags as I have offered in the article, you may find that you get the error:

The type for attribute xxx of tag yyy could not be determined.

where xxx is the attribute you're using and yyy is the tag whose attributes it's complaining about.

Though I didn't mention that error specifically, I did say that it was my experience that you needed to restart the server upon placing a new tag into the web-inf\lib directory.

This error is what you'll see if you don't.