Return-Path: 
 <user-return-135916-apmail-struts-user-archive=struts.apache.org@struts.apache.org>
Delivered-To: apmail-struts-user-archive@www.apache.org
Received: (qmail 32712 invoked from network); 2 May 2005 21:39:00 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 2 May 2005 21:39:00 -0000
Received: (qmail 86912 invoked by uid 500); 2 May 2005 21:40:05 -0000
Delivered-To: apmail-struts-user-archive@struts.apache.org
Received: (qmail 86871 invoked by uid 500); 2 May 2005 21:40:05 -0000
Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:user-unsubscribe@struts.apache.org>
List-Subscribe: <mailto:user-subscribe@struts.apache.org>
List-Help: <mailto:user-help@struts.apache.org>
List-Post: <mailto:user@struts.apache.org>
List-Id: "Struts Users Mailing List" <user.struts.apache.org>
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Delivered-To: mailing list user@struts.apache.org
Received: (qmail 86834 invoked by uid 99); 2 May 2005 21:40:04 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=RCVD_BY_IP
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: domain of craigmcc@gmail.com designates
 64.233.170.201 as permitted sender)
Received: from rproxy.gmail.com (HELO rproxy.gmail.com) (64.233.170.201)
  by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 02 May 2005 14:40:04 -0700
Received: by rproxy.gmail.com with SMTP id i8so916557rne
        for <user@struts.apache.org>; Mon, 02 May 2005 14:38:30 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=bsUVNCuFbhFA90PdFF4C0g8u76lEtAhmRwajQJUlCju1X0kwCY1qMrf4lXpdc3pFew+2JpuujdB+BuEFVKwwUOQ7M3i1S0aDQ89z5qn7PiKg/mdQ/xU82PmdAVMIix0pe5PtICwRHZpjl44Iv+J8G53ROa2DoB/MocrVAPxCFtw=
Received: by 10.38.92.79 with SMTP id p79mr6588956rnb;
        Mon, 02 May 2005 14:38:30 -0700 (PDT)
Received: by 10.39.3.49 with HTTP; Mon, 2 May 2005 14:38:29 -0700 (PDT)
Message-ID: <f8b39ace050502143863c8c988@mail.gmail.com>
Date: Mon, 2 May 2005 14:38:29 -0700
From: Craig McClanahan <craigmcc@gmail.com>
Reply-To: craigmcc@apache.org
To: Struts Users Mailing List <user@struts.apache.org>
Subject: Re: [OT] Re: ajax proj
In-Reply-To: <20050502210945.93497.qmail@web41213.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <20050502210945.93497.qmail@web41213.mail.yahoo.com>
X-Virus-Checked: Checked
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

On 5/2/05, Woodchuck <woodchuck_5@yahoo.com> wrote:

> JSTL is da bomb!  :)

Indeed it is.  If you actually need to create XML in a response to an
XmlHttpRequest call from an Ajax client side gadget :-), here's an
approach using a JSP 2.0 page (in xml syntax) that uses JSTL to
iterate over a result set, and JSP expressions to pull out the data
(copied from the Shale Use Cases example app):

--------------------
<jsp:root             version=3D"2.0"
                      xmlns:c=3D"http://java.sun.com/jsp/jstl/core"
                    xmlns:jsp=3D"http://java.sun.com/JSP/Page">

  <jsp:directive.page
                  contentType=3D"text/xml;charset=3DUTF-8"/>

  <categories>
    <c:forEach            var=3D"category"
                        items=3D"${lookup$listCategories.supportedCategorie=
s}">
      <category>
        <label>${category.label}</label>
        <value>${category.value}</value>
      </category>
    </c:forEach>
  </categories>

</jsp:root>

--------------------

The business logic that looks up the label/value pairs for the
response doesn't have a clue how it will actually be rendered, and
setting up a JSP page is much easier to author than building an XML
DOM in Java code.

Craig


>=20
> --- Rick Reumann <struttin@reumann.net> wrote:
> > Dakota Jack wrote the following on 5/2/2005 4:01 PM:
> > >
> > > The other aspect that is not discussed above is the removal of the
> > > complexity from the "page".  This is where JSP, Taglibs, etc., come
> > > into the picture.  And, I suspect, you two are talking about a
> > > combination of this problem (keeping the page simple) and the
> > previous
> > > problem (using a reasonable architecture).
> >
> > yes. For example, take a table sort example. I like being able to use
> >
> > JSTL (or even a display tag if that suits you) to display the
> > collection
> > info into the display of the table.
> >
> > Doing something like this within a servlet (Action) wouldn't really
> > be
> > wrong, but just more difficult to maintain and more of pain to code
> > (using StringBuffer and append bla bla).
> >
> > --
> > Rick
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> > For additional commands, e-mail: user-help@struts.apache.org
> >
> >
>=20
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>=20
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org