Thanks for the reply Salil. But I disagree with your reply:
just see at the end of page 349 it is mentioned that user want one more instance of same name of same bean but want to set the properly again.
So in the second senario we have changed the scope of the bean . In this case two instances of the same bean will exist one at request scope and the second at page scope.
When the non-nested <jsp:setProperty> tag is used, it resets the bean's property value had the bean already existed. But when <jsp:setProperty> is nested inside the body of <jsp:useBean>, the property setting is conditional and the values will be set only if a new bean is created. ie., there is only one instance of the bean and it exists at page scope.
But I am quite confused by the change of scope in the examples. I checked the errata section of the book given online but didn't find anything regarding this. I know it is not an error per se, but I am puzzled and was wondering if there is any requirement in the specification that demands for a change of scope to a more restrictive one as given in the cited problem. Thank you.
