I have many existing business logic java classes from that we now want to re-use as beans in a JSP app. The classes weren�t designed for a servlet environment, use member variables and are sizable so we don�t want to create them for each request (I�m assuming it�s costly). Yet we need the member variables to be specific to one thread during a given request cycle and we don�t want to re-write the classes. To complete this, could we pool these beans like we would database connections? We would have a pool of x instances of the beans at an application scope level. Then each would be checked out and checked in as needed. Would this make the member variables �thread safe� because the instance is checked out to one request? In other words, would this make sure that if thread 1 changed a member variable value, thread 2 couldn�t change it because it would be assigned a different instance of the bean? Seems like it should be fine to me but I thought I should ask the group. Has anyone tried this or have any thoughts? I know it would take up more memory having a pool of instances around but my gut feel is this is better than creating the objects with each request. Thanks in advance, >David D =========================================================================== 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
