Re: JSP BEAN RETRIEVAL

From:

Lew <lew@lewscanon.com>

Newsgroups:

comp.lang.java.programmer

Date:

Tue, 11 Mar 2008 00:54:09 -0400

Message-ID:

<vJ-dndfH0-jsjUvanZ2dnUVZ_q2hnZ2d@comcast.com>

Vittorix wrote:

Arne Vajh?Wj wrote:

because I couldn't find a solution, I'm using a scriplet inside the
JSP that does the job:

    int numBooks = Integer.parseInt(request.getParameter("numBook"));
    for (int i=1; i<=numBooks; i++)
    {
        String bookBeanS = "bookBeanBeg" + i + "";
        p4Solution.BookBean bookBean = null;
        bookBean = (p4Solution.BookBean)
        session.getAttribute(bookBeanS);
    out.write(bookBean.getSeq_no()); }

JSP pages with scriptlets with out.print/write should not
be able to pass code review.

what do you mean? it works great

He means that the presence of scriptlet in a JSP is a "bad" mark in a code
review. It presents maintenance difficulties, and obviates the natural
separation of view artifacts from logic artifacts. It also represents that
you left a bug unfixed, in that the <c:forEach> idiom should work, so from an
organizational standpoint that remains an open issue.

I have known a few people who had Marty Hall as a teacher. He took off ten
points from an assignment submission for each line of scriptlet in a JSP.
<http://www.apl.jhu.edu/~hall/>

--
Lew