Hi, I have a few uncleared points about jsp:useBeans. First, beans that have scope of "session" or "application" can persist throughout a session. So what effect does that have on using HttpSession object? What are "session beans" and "application beans" equivalents in servlets? Do they just place a session bean inside a HttpSession object? Secondly, when is proper to use <jsp.useBean getProperty id="someBean" Property="Tree"/> and when to use <%someBean.getTree()%>? Overall, I feel that JSP is much simpler and flexible than servlets.
Secondly, when is proper to use <jsp.useBean getProperty id="someBean" Property="Tree"/> and when to use <%someBean.getTree()%>?
Arguments about this sometimes verge on the religious debate. The former is just a slightly more verbose, tag-based version of the latter. I personally tend to favour the tag, because I think moving Java out of the JSP is a Good Thing.
Overall, I feel that JSP is much simpler and flexible than servlets.
Depending on what you want to do, it can be a lot simpler. But it also can encourage incredibly sloppy coding. - Peter
In line with that, the latest reference implementation of the Java Pet Store almost completely removes java code from JSP, relying on tags. The bluprints recommend using JSP for the view portion, and Servlets for the controller portion. Regards, Mark