This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Originally posted by Brian Percival: you are right.. jstl/el is designed to work with Beans. But useBean ussage would mean, we need to have extra knowledge of knowing if a class fits the Bean rules.
I don't get the point,. This applies no matter how the bean gets instantiated. If it's going to be a scoped variable accessible by the EL, it must be a bean.
I would rather be comfortable somehow using c:set and then accessing the values I want.
<c:set> has no means to cause a bean to become instantiated as that is not its purpose. That's what <jsp:useBean> is for.
If you'd rather not use <jsp:useBean> on a page for whatever reason (which I still don't get), instatiate the bean in the servlet controller and set it as a scoped variable prior to forwarding to the page.