Kamal Tripathi wrote:First of all I think there is a little code issue here
has not been written as a scriptlet, instead the line should have been
Amit Prakash Singh wrote:
But option E is debatble : because as per HFSJ page - 260: "make sure your attribute class types are Serializable and you never have to worry about it.But if they�re not Serializable (which could be because one of the attribute object�s instance variables is not Serializable), have your attribute object class implement HttpSessionActivationListener and use the activation/passivation callbacks to work around it"
So object must be serializable doesn't holds true according to the comment?
sridhar row wrote:
Sorry to open an old thread...but I feel even B is not the right answer as BEGINNER will still be able to access resources in directory2 using HTTP methods other than GET..Please correct me if I'm wrong.
Venkat Yerramsetty wrote:
Does that mean, session listeners no matter the order in the DD with mixup of context listeners will be called prior to the context listeners, and if we have a couple of session listeners then their order would have to be taken care by the developer?
Ankit Garg wrote:To test this I think you'll have to make a custom doHead request to a servlet using java.net.Socket or java.net.URL class. If there is any other easier way then I don't know about it...
Milton Ochoa wrote:can you give us, you opinion, why not is suitable
Ankit Garg wrote:
Well I created a program to test this. I wrote a servlet in which I wrote some response and then included another srevlet in it. And it worked. The only thing the included servlet can't do is to set the response headers.