Just did a re-install of Tomcat on my computer at home last night (gotta love 
reformatting). It does NOT come with the JSTL standard tag libraries. Have to download 
them from the Taglibs section of Jakarta and install them yourself.

Keith

---------- Original Message -----------
From: "Karl Coleman" <[EMAIL PROTECTED]>
To: "Tag Libraries Users List" <[EMAIL PROTECTED]>
Sent: Fri, 21 May 2004 09:47:43 -0400
Subject: RE: passing JSTL to custom tag attribute

> It implements EL natively since it is a JSP 2.0 container. But including JSTL is 
> news 
to me as well.
> 
> Karl
> 
> -----Original Message-----
> From: Derek Mahar [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 21, 2004 9:45 AM
> To: Tag Libraries Users List
> Subject: RE: passing JSTL to custom tag attribute
> 
> Are you sure about this?  Tomcat 5 does not ship with jstl.jar and standard.jar 
> which 
are the standard JSTL distribution files.  Does it hide JSTL in some other JAR file(s).
> 
> Derek (M)
> 
> -----Original Message-----
> From: Derek [mailto:[EMAIL PROTECTED] 
> Sent: May 20, 2004 8:33 PM
> To: Tag Libraries Users List
> Subject: Re: passing JSTL to custom tag attribute
> 
> No, actually you don't have to in Tomcat 5.  It does ship with JSTL 
> built in.  You just have to use the appropriate declarations in the 
> web.xml and so on.
> 
> Derek (H)
> 
> On May 20, 2004, at 5:04 PM, Derek Mahar wrote:
> 
> > What do you mean when you say that Tomcat 5 implements JSTL 
> > "natively"? From my experience, Tomcat 5 does not ship with JSTL.  You 
> > must download and install JSTL separately.
> >
> > Derek
> >
> > -----Original Message-----
> > From: Karr, David [mailto:[EMAIL PROTECTED]
> > Sent: May 13, 2004 9:14 AM
> > To: Tag Libraries Users List
> > Subject: RE: passing JSTL to custom tag attribute
> >
> >
> > I would say there are several basic ideas here:
> >
> > 1. Use a JSP 2.0 container, like Tomcat 5.  The JSTL is implemented 
> > natively there.
> >
> > 2. Use solution 1.
> >
> > 3. Build a second tag library that's implemented exactly like
> > Struts-EL.
> > Each tag class in Struts-EL is a subclass of the corresponding tag in
> > the base library, and the only functionality in the Struts-EL tag is to
> > pass the attribute value through the EL engine from the Jakarta JSTL
> > implementation.
> >
> > 4. Do not build a tag library that implements your business logic AND 
> > references the Jakarta EL engine.  When you move to a JSP 2.0 
> > container, you'll then have to spend more time yanking it out.
> >
> >> -----Original Message-----
> >> From: Paul Wallace [mailto:[EMAIL PROTECTED]
> >> Sent: Wednesday, May 12, 2004 8:15 PM
> >> To: [EMAIL PROTECTED]
> >> Subject: passing JSTL to custom tag attribute
> >>
> >>
> >> Hi,
> >>      I wish to call a custom tag, passing a dynamic value for its 
> >> attribute. I retrieve the value thus:
> >>
> >> <c:set var="userid" value="${param.userid}"/>
> >>
> >> and I wish to call my custom tag passing 'userid' as an attribute. 
> >> Curently I have:
> >>
> >> <my:execute userid="${userid}">
> >>
> >> but the literal string "${userid}" is passed into the handler. To 
> >> acheive the desired results I could of course use:
> >>
> >> <my:execute userid="<%= request.getParameter("userid") %>">
> >>
> >> but that would mean embedding JSP, when I wish to encompass all logic 
> >> in tags. Does anyone have any suggestions how I might pass the JSTL 
> >> value, dynamically to the attribute of my custom tag please?
> >>
> >> Thanks
> >>
> >> Paul.
> >>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> > NOTICE: This email contains privileged and confidential information
> > and is intended only for the individual to whom it is addressed. If 
> > you are not the named addressee, you should not disseminate, 
> > distribute or copy this e-mail. Please notify the sender immediately 
> > by e-mail if you have received this transmission by mistake and delete 
> > this communication from your system. E-mail transmission cannot be 
> > guaranteed to be secured or error-free as information could be 
> > intercepted, corrupted, lost, destroyed, arrive late or incomplete, or 
> > contain viruses.
> >
> > AVIS: Le présent courriel contient des renseignements de nature
> > privilégiée et confidentielle et n'est destiné qu'à la personne à qui 
> > il est adressé. Si vous n'êtes pas le destinataire prévu, vous êtes 
> > par les présentes avisés que toute diffusion, distribution ou 
> > reproduction de cette communication est strictement interdite.  Si 
> > vous avez reçu ce courriel par erreur, veuillez en aviser 
> > immédiatement l'expéditeur et le supprimer de votre système. Notez que 
> > la transmission de courriel ne peut en aucun cas être considéré comme 
> > inviolable ou exempt d'erreur puisque les informations qu'il contient 
> > pourraient être interceptés, corrompues, perdues, détruites, arrivées 
> > en retard ou incomplètes ou contenir un virus.  
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
------- End of Original Message -------


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to