Answer the question
In order to leave comments, you need to log in
Should I be concerned about how well HttpServlet implements Serializable?
Please share your experience, if you had to develop / design applications (work in a cluster, something else) that took this fact into account: HttpServlet implements Serializable. What real cases did you have?
Should I be concerned about the correctness of the implementation of the HttpServlet successor?
There have been discussions on SO about this topic:
Why does HttpServlet implement Serializable?
Why is HttpServlet in java implements serializable?
Answer the question
In order to leave comments, you need to log in
IMHO, having stateful servlets is not good. And if they are stateless, then why all this?
There are sessions for this (and ideally it would be necessary without them).
Almost the entire modern world of Enterprise-Java lives on the use of servlets. And no one really cares that HttpServlet implements Serializable . And I have a question - how can you implement Serializable poorly if it is a marker interface that does not imply the implementation of any methods? Serialization of Serializable objects is handled by Java itself. I think that there is no need to worry about this issue, but the question "Why?" must be addressed to the JCP.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question