RE: bean:define vs c:set

or the upgrade to tomcat 5. > > > Kris. > > -Oorspronkelijk bericht- > Van: Craig McClanahan [mailto:[EMAIL PROTECTED] > Verzonden: donderdag 29 juli 2004 18:25 > Aan: Struts Users Mailing List > Onderwerp: Re: bean:define vs c:set > > You are correct tha

RE: bean:define vs c:set

nahan [mailto:[EMAIL PROTECTED] Verzonden: donderdag 29 juli 2004 18:25 Aan: Struts Users Mailing List Onderwerp: Re: bean:define vs c:set You are correct that does not create a scripting variable, so you can't use the specified identifier in a scriptlet. The question, though, is why are

Re: bean:define vs c:set

You are correct that does not create a scripting variable, so you can't use the specified identifier in a scriptlet. The question, though, is why are you still using a scriptlet expression? Why not use an EL expression instead? or, to avoid needing to do the in the first place: The a

RE: bean:define vs c:set

creates a scoped attribute AND a scripting variable, whereas just created the scoped attribute. In your example you are making use of the scripting variable feature (as the data is already available as a scoped attribute). But, with JSP2, all tags magically become EL aware (I believe). So you sh