I have an abstract controller support class for searches and result lists:
@Controller
@SessionAttributes("query")
public abstract class SearchController<Q extends SearchQuery> {
@RequestMapping
public String performSearch(@ModelAttribute("query") Q query) {
....
}
@ModelAttribute("query")
public abstract Q createDefaultSearchQuery();
}
Several actual search controllers extend this base class.
After having accessed one of the controllers (say /searchBooks.html
using BookSearchQuery implements SearchQuery
) the query is correctly stored in the session, available for subsequent requests.
However, when I access another controller (say /searchAuthors.html
using AuthorSearchQuery implements SearchQuery
) the query from the last request (BookSearchQuery
) is still being used for the new controller causing a ClassCastException
later on.
I have tried moving the @SessionAttribute
annotation from the support class to the implementation classes, to no avail.
Is there something I'm doing wrong or is this by design? What can I do?
Thanks a lot!
I just tried this on Spring 3.0.2 and the session attributes are not shared between controllers. In fact I was looking for the opposite effect and that's how I found out.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With