Originally posted by saumil baxi:
Try using pageContext.getParameter to get the value in your scriptlet
In a properly organized web application, it's generally much faster to do it right with JSTL and EL.Originally posted by saumil baxi:
i agree but I guess it would be in ideal condition. Time crunch and work load leads us to use scriptlets which can do your things faster rather then taglib.
Originally posted by saumil baxi:
u can get the ...
<%=pageContext.getAttribute(PARAMETER NAME)%>
Bauke Scholtz wrote:I repeat, it is a bad practice. This isn't 1998. This is 2008.
Bauke Scholtz wrote:Fine, but why are you resurrecting an old topic for that?
Bauke Scholtz wrote:Workarounding a bug caused by 3rd party isn't still a valid reason to use scriptlets. You could perfectly use a servlet or javabean for this.
Bauke Scholtz wrote:After all I would still push IBM to get that bug fixed or so.
Rune Hellem wrote:
Bauke Scholtz wrote:I repeat, it is a bad practice. This isn't 1998. This is 2008.
But sometimes you might have to do it even if it is bad practice, currently facing a problem on WebSphere Portal where I don't get fmt:formatDate or my custom taglib to work. My post on IBM DW. So for the time being I have to use scriptlet in my app when deploying on WebSphere![]()
Water proof donuts! Eat them while reading this tiny ad:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
|