Container callback methods are those that you write expecting that the container will call them. Inline methods, as you are calling them, I believe are methods that you call.
As an example, see in the Filter API that each of its 3 methods are called by the container - they are all container callback methods. [ March 14, 2007: Message edited by: Marc Peabody ]
Pg 700, K&B mentions doFilter as both callback and an inline function. The reason could be is because apart from getting called by the container, the devloper himself could put in a call to doFilter(request,response) to call the next filter/servlet in chain. [ March 14, 2007: Message edited by: Aniket Patil ]
Satou I have seen a question about callback functions in filter API in Filters chapetr of HFSJ book. In the answer the destroy()is selected as callback function. On other thing is that we call chain.doFilter() to invoke next filter in chain. Is this call not making doFilter() an inline method.
You should be more specific when asking. If I'm correct, question is : Q1: Which are true about filters? C. The doFilter method is always a container callback method.
They don't specify which doFilter it is. Question is about filters, not the Filter class only.
Filter.doFilter is a container callback, but FilterChain.doFilter is an inline method. A dirty trick, which fortunately won't have at the exam