Solved

HttpServlet and ServletRequestAttributeListener explantion

Posted on 2015-02-01
3
45 Views
Last Modified: 2015-02-11
This is from the book I am reading:

Given this code from an otherwise valid HttpServlet that has also been
registered as a ServletRequestAttributeListener:

public void doGet(HttpServletRequest req, HttpServletResponse res) throws IOException, ServletException {
         req.setAttribute(“a”, “b”);
         req.setAttribute(“a”, “c”);
          req.removeAttribute(“a”);
}
        public void attributeAdded(ServletRequestAttributeEvent ev) {
        System.out.print(“ A:” + ev.getName() + “->” + ev.getValue());
}
       public void attributeRemoved(ServletRequestAttributeEvent ev) {
       System.out.print(“ M:” + ev.getName() + “->” + ev.getValue());
}
       public void attributeReplaced(ServletRequestAttributeEvent ev) {
       System.out.print(“ P:” + ev.getName() + “->” + ev.getValue());
}

Open in new window


What logging output is generated?

And answer is:
C. A:a->b P:a->b M:a->c

And explanation from book is:
Tricky! The getValue method returns the OLD value of the attribute if the attribute was replaced.

My question is how this could be?
Particularly this part of sequence is not clear to me: P:a->b
Why would it be once again P:a->b instead of P:a->c ?
0
Comment
Question by:KPax
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 28

Accepted Solution

by:
dpearson earned 500 total points
ID: 40583362
Just to clarify this output, can we call them "Added", "Replaced" and "Removed" so we're looking at this:

Added:a->b
Replaced:a->b
Removed:a->c

Now the question is why does Replaced return "b" for the value instead of "c"?

The simple answer is because that's what the docs say it should do:
http://docs.oracle.com/javaee/7/api/javax/servlet/ServletRequestAttributeListener.html

void attributeReplaced(ServletRequestAttributeEvent srae)
Receives notification that an attribute has been replaced on the ServletRequest.
Parameters:
srae - the ServletRequestAttributeEvent containing the ServletRequest and the name and (old) value of the attribute that was replaced


Now maybe the more interesting question is why are they doing this?

Well usually APIs like this are designed to pass you the old value, because you always have the option to ask for the current value in the callback.  So if they pass you the old value - you have more information available to you than if they just passed in the current value.  (There's no way to ask "what value did this attribute use to have?" after it's gone).

So with this API design you could write a listener than took some action whenever the "a:b" was removed - either by an explicit remove call or by replacing it with another value.  If they only passed in the new value, you couldn't write that listener (without storing the values that were added yourself).

Hope that helps make it clearer why it's this way.

Doug
0
 

Assisted Solution

by:KPax
KPax earned 0 total points
ID: 40593317
I found this explanation as well

The getName() method returns the String name of the attribute that triggered the event. The getValue() method returns the object value of the attribute that triggered the event. Watch out! It returns the old value, not the new one. In other words, it returns the value the attribute had BEFORE the change that triggered the event!
0
 

Author Closing Comment

by:KPax
ID: 40602721
I found this solution in a book  "Servlets and JSP, 2 ed"
0

Featured Post

[Live Webinar] The Cloud Skills Gap

As Cloud technologies come of age, business leaders grapple with the impact it has on their team's skills and the gap associated with the use of a cloud platform.

Join experts from 451 Research and Concerto Cloud Services on July 27th where we will examine fact and fiction.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Java contains several comparison operators (e.g., <, <=, >, >=, ==, !=) that allow you to compare primitive values. However, these operators cannot be used to compare the contents of objects. Interface Comparable is used to allow objects of a cl…
Introduction Java can be integrated with native programs using an interface called JNI(Java Native Interface). Native programs are programs which can directly run on the processor. JNI is simply a naming and calling convention so that the JVM (Java…
Viewers learn how to read error messages and identify possible mistakes that could cause hours of frustration. Coding is as much about debugging your code as it is about writing it. Define Error Message: Line Numbers: Type of Error: Break Down…
The viewer will learn how to implement Singleton Design Pattern in Java.

617 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question