At 11:54 PM -0700 4/21/04, Gogineni, Pratima wrote:
We have bean:write tags that read bean properties and output to the jsp
page.
I am wondering why we are always forced to set bean properties through one
of the form tags.
...
I saw the jstl c:set tag but that is not as powerful as the struts bean tags
in terms of dealing with indexed properties. So I have had to write a custom
tag for this. It seems fairly straight forward to do this & hence I am
wondering why the standard struts tag library doesnt contain this.  Im
wondering if this violates some design principle in struts.

The priniciple would probably be "focus." The Struts JSP tags are not the primary focus of Struts (although they seem to be the most recognized characteristic.) With the emergence of the JSTL as well as the recognition that JSP itself is not the preferred view technology of choice for all users, Struts has turned its focus on the "controller" layer.


In my opinion, the only Struts JSP tags should be those which coordinate tightly with the controller: the ones which know specifically where to find and how to handle objects that the controller passes out to the view. This is not only to help keep Struts focused, but to encourage ideas that would be useful in non-Struts environments to be developed in a more interchangeable way.

(As an aside, I was at the Milwaukee "No Fluff, Just Stuff" symposium last weekend and there was a fair bit of talk about how to use Tiles outside of Struts, including a presentation on the same by David Geary [who also called Tiles the best technology "since sliced bread," or something similarly hyperbolic]. Anyway, I wonder how we might think about that when reorganizing en route to TLP-status.)

Joe

--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining."
-- Jef Raskin


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



Reply via email to