I'm really not sure what you are asking for. EJBs (entity beans, at least) are stateful, potentially data-heavy objects, which it makes sense to "swap out" if they are not being used. Servlets, on the other hand, are essentially stateless protocol adapters to convert HTTP requests to method calls on other objects. I can't see what benefit there would be from "passivating" a servlet. Can you explain a bit more about what you are trying to achieve?
Hi Frank, What I was really looking for is, just as in entity bean, where we store a state, similarly in a servlet I want to store some state of database, i.e particular values, but would like to use session, is there some other way that the container can store it. Hope I am clear. Thnx Anyway MB
What are you doing? You are supposed to be reading this tiny ad!
the new thread boost feature brings a LOT of attention to your favorite threads