Return-Path: 
 <taglibs-user-return-5529-qmlist-jakarta-archive-taglibs-user=nagoya.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-taglibs-user-archive@apache.org
Received: (qmail 43178 invoked from network); 6 May 2003 17:17:33 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 6 May 2003 17:17:33 -0000
Received: (qmail 12615 invoked by uid 97); 6 May 2003 17:19:37 -0000
Delivered-To: qmlist-jakarta-archive-taglibs-user@nagoya.betaversion.org
Received: (qmail 12608 invoked from network); 6 May 2003 17:19:37 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by nagoya.betaversion.org with SMTP; 6 May 2003 17:19:37 -0000
Received: (qmail 40717 invoked by uid 500); 6 May 2003 17:17:07 -0000
Mailing-List: contact taglibs-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:taglibs-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:taglibs-user-subscribe@jakarta.apache.org>
List-Help: <mailto:taglibs-user-help@jakarta.apache.org>
List-Post: <mailto:taglibs-user@jakarta.apache.org>
List-Id: "Tag Libraries Users List" <taglibs-user.jakarta.apache.org>
Reply-To: "Tag Libraries Users List" <taglibs-user@jakarta.apache.org>
Delivered-To: mailing list taglibs-user@jakarta.apache.org
Received: (qmail 40704 invoked from network); 6 May 2003 17:17:06 -0000
Received: from phobos-adm.email.arizona.edu (HELO phobos.email.Arizona.EDU)
 (128.196.133.165)
  by daedalus.apache.org with SMTP; 6 May 2003 17:17:06 -0000
Received: from James (128.196.82.115) by phobos.email.Arizona.EDU (6.7.016)
        id 3EB7AEE10000A5AB for taglibs-user@jakarta.apache.org;
 Tue, 6 May 2003 10:17:08 -0700
Message-ID: <002b01c313f3$527a6700$7352c480@finearts.arizona.edu>
From: "James Smith" <jksmith@email.arizona.edu>
To: "Tag Libraries Users List" <taglibs-user@jakarta.apache.org>
References: <20030506164732.21915.qmail@web10003.mail.yahoo.com>
Subject: Re: Populating One <select> Based On The Value In Another
Date: Tue, 6 May 2003 10:17:07 -0700
Organization: University of Arizona
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

You can't go from JavaScript back to JSTL without another trip to the
server; however, you certainly can use JSTL tags to create a map within
JavaScript code, something like this:

<sql:query var="rs">
    select ID, Name from tblSomeTable
</sql:query>

<script language="javascript">
    firstSelectHashMap = new Array();
    <c:forEach var="row" items="${rs.rows}">
        <sql:query var="rs2">
            select ID, Name from tblChildTable where ParentID = ?
            <sql:param value="${row.ID}" />
        </sql:query>
        secondSelectHashMapChoice = new Array();
        <c:forEach var="row2" items="${rs2.rows}">
            secondSelectHashMapChoice['<c:out value="${row2.ID}" />'] =
'<c:out value="${row2.Name}" />';
        </c:forEach>
        firstSelectHashMap['<c:out value="${row.ID}" />'] = tempChild;
    </c:forEach>
</script>

My JavaScript is a bit rusty but it should look something like that.
Anyway, that whole piece of code makes your page a lot larger, and then,
when a select occurs, you've got to write the JavaScript to depopulate your
second select box and repopulate it with the chosen
secondSelectHashMapChoice.  So it's possible to code but it seems fairly
nasty.  The second trip to the server is probably much wiser, unless a
JavaScript guru out there has a brilliant method, probably involving forcing
submits from forms within internal frames hidden by moving them off the page
with CSS-P.

James Smith
Application Systems Analyst, Treistman Center
College of Fine Arts, University of Arizona

----- Original Message ----- 
From: "Michael Duffy" <duffymo@yahoo.com>
To: "Tag Libraries Users List" <taglibs-user@jakarta.apache.org>
Sent: Tuesday, May 06, 2003 9:47 AM
Subject: RE: Populating One <select> Based On The Value In Another


>
> I've got a front controller servlet that takes
> requests, executes commands, puts results into the
> request, and forwards them onto the next page.  The
> next page can certainly do this:
>
> <jsp:useBean id="something" class="java.util.Map"/>
>
> Now I can access the map by writing:
>
> "${something['key']}"
>
> If the Map has String keys and java.util.List values,
> I can get the value and stuff it into a JSTL
> <c:forEach> tag.
>
> Actually , I haven't gone to ANY trouble yet because
> I've just started on this effort.  ;)  It was just an
> idea.  I thought that if there was a way to get the
> value out of DHTML and into JSTL that I was ignorant
> of I'd be glad to know it.
>
> But the dearth of information has brought me to the
> same conclusion that you're drawing: it's not
> possible.  I'll just populate both drop-downs at the
> same time.  Thanks. - MOD
>
>
> --- Wendy Smoak <Wendy.Smoak@asu.edu> wrote:
> > Michael wrote:
> > > Exactly.  It's a choice between doing it on the
> > client
> > > side or enduring another round-trip to the server.
> >  I
> > > know how to get it from the server, but I was
> > hoping
> > > that I could send a java.util.Map down when the
> > page
> > > is rendered and save myself a trip.
> >
> > All the Java/JSP/JSTL code executes on the server,
> > so I don't see where you
> > could "send" a Map down to the client side.  Maybe
> > an applet?  You could
> > surely render the *contents* of the Map into a
> > JavaScript data structure.
> > (Does JavaScript have a Map structure?) And then use
> > client-side JavaScript
> > to populate the second drop-down once the user has
> > made a selection from the
> > first.
> >
> > > But this is the first time I've had the problem of
> > > populating one drop-down using the choice from
> > > another.  I know how to get the selection from the
> > > first box out of JavaScript.  Getting that value
> > into
> > > JSTL and the EL is the thing that I'm fuzzy on.
> >
> > It's one or the other.  Since JavaScript is
> > client-side, and JSTL/EL is
> > server-side, you can't get the value out of
> > JavaScript and into JSTL.  If
> > you want to save a trip to the server, then I don't
> > believe JSTL will be of
> > any help.
> >
> > How much of a load will this site be under?  Is an
> > extra round trip to the
> > server really that important?  You may be going to a
> > lot of trouble to avoid
> > something that isn't really going to be a problem.
> >
> > -- 
> > Wendy Smoak
> > Applications Systems Analyst, Sr.
> > Arizona State University PA Information Resources
> > Management
> >
>
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: taglibs-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: taglibs-user-help@jakarta.apache.org
>


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