I'm working on Servlets-4b while awaiting nitpick on Servlets-4a. I want to refactor the code from Servlets-4a in small steps so I'm dancing around that working code so I don't break it. My thinking is that I can add logic around that code to effectively secure it without getting into an endless loop. It's not working.
I'm having a real tough time figuring out where to place the decision logic inside the servlet. I'm trying to think polymorphically and logically at the same time and getting all jammed up!
Knowing that the servlet demands an action, keeps pointing me to mess with my inner classes. I really don't want to do that, do I? :roll:
Marilyn de Queiroz
posted 7 years ago
You might want something that all your inner classes have access to.
JavaBeginnersFaq "Yesterday is history, tomorrow is a mystery, and today is a gift; that's why they call it the present." Eleanor Roosevelt