Hi Matthew,
Thanks for your sharing. It helps me a lot.
I was wondering why you talked about POJOs could be threaded ? The
request processing itself is already multi-threaded before your pojos
are called, so I don't see the need to worry about it. Resin and all
application server start a
Ricardo,
Should have said thread safe. I was thinking to make the POJOs reusable to
allow for fewer objects to be created. As it stands now, every requests
instantiates and destroys a handler POJO. From time to time I consider
restructuring these into a worker queue of instantiated objects to
I have one singleton instance of each of my pojos, processing the
requests. They are created only at startup time by the main controller,
and called by my main controller depending of the request url.
I don't think there is any refactoring difficulties changing a per
request creation into a
On 3/21/13 10:51 AM, Riccardo Cohen wrote:
Hello
I'm refactoring my url requests processing and need some advice. I've
learnt mostly by myself, and I'm not sure to make the good choices.
Presently my request processing is a mixing of servlet configurations like :
servlet-mapping
I share your fear of frameworks so I created my own request handlers using
Resin 4 and a couple of simple classes. Not sure why you specifically want to
handle JSP requests with a servlet so I might be missing something but:
I put all my JSPs under WEB-INF for privatization
