Hello all,
Can someone point out a few servlet design patterns and general
observations when it comes to such development?
I'm familiar with the common one of having a servlet for every webpage,
but I'm trying to come up with a way of adding new webpages to an
existing servlet without having to worry about the servlet implementation
every time.
The way I'm thinking of implementing it is to have a class for every
webpage associated (not talking about the actual *html* code) with the
servlet and an interface which will define the way they interact.
So the servlet should have a HashMap with all the associated webpages and
each time will get the correct one depending on the request and use it.
This ofcourse is just something that I have in mind.
I'm trying to give food for thought here. :)
Thanks in advance,
Markos Charatzas
Can someone point out a few servlet design patterns and general
observations when it comes to such development?
I'm familiar with the common one of having a servlet for every webpage,
but I'm trying to come up with a way of adding new webpages to an
existing servlet without having to worry about the servlet implementation
every time.
The way I'm thinking of implementing it is to have a class for every
webpage associated (not talking about the actual *html* code) with the
servlet and an interface which will define the way they interact.
So the servlet should have a HashMap with all the associated webpages and
each time will get the correct one depending on the request and use it.
This ofcourse is just something that I have in mind.
I'm trying to give food for thought here. :)
Thanks in advance,
Markos Charatzas
Comment