since it is clear from the earlier discussion that JSP authors need be as mindful of multi-threading issues as servlet programmers, i'm wondering whether there is a tool to us. c has lint, which inspects code for semantic errors [sort of, anyway]. what i'm thinking of might be just a compiler switch [no idea how it could be implemented], which flags "shared resources" as being vulnerable. for regular classes, this might be driven by the keyword thread. for servlets, which are threaded anyway, it is a bit more complicated i guess. does anyone know of such a product? existing or in process?? thanx, robert young =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". FAQs on JSP can be found at: http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.html