I had the same feeling that servlet spec. should be more specific when
I just started working with J2EE:)
But, my experience tells me that a specification tells you "What" you
need to have in a servlet container and not "How" to implement a
servlet container.
If I want to learn servlet programmin
Good point. I guess the J2EE tutorial would be the place for stuff like
that (I was trying to only speak of "official" documentation).
Erik
Craig McClanahan wrote:
It's important to remember that the Servlet Specification target
audience isn't application developers -- it's people that are
implem
It's important to remember that the Servlet Specification target
audience isn't application developers -- it's people that are
implementing servlet containers (such as the group that creates
Tomcat). It is about defining requirements, not illustrating use
cases.
For application level questions, a
Ack, here I go being a writing critic and leave in a glaring typo . . .
Erik Weber wrote:
Well, I have to criticize my own advice. I just read over the Servlet
2.4 spec. It doesn't explain this well at all, in my opinion. It still
uses the same old, nearly meaningless, obscure language like "used
Well, I have to criticize my own advice. I just read over the Servlet
2.4 spec. It doesn't explain this well at all, in my opinion. It still
uses the same old, nearly meaningless, obscure language like "used by
the Servlet container to communicate with a Servlet", and stuff like
that, which doe
5 matches
Mail list logo
