Craig McClanahan wrote:
The *standard* UI components weren't meant to be compelling -- they
were meant to give people an opportunity to actually explore the APIs
without having anything except a JSF implementation.
Fair enough. By the way, I'm not bagging on the UI components in any
way. The one that looks the most intriguing to me is the "rendered"
attribute that comes with the various widgets. That attribute combined
with the EL is sweet! Currently I have my own custom tags to check for
field availablility and editability. I perform two checks for every
field with two tags (ex. <isEditable> and <isNotEditable>). The
rendered attribute combined with EL could condense my code (and get rid
of the need for two custom tags!)
indeed, the integration library hooks the two frameworks
together only when processing an action event from a submit buttton or
hyperlink).
Interesting. Thanks for this nugget. This helps with my "behind the
scenes" understanding of what you're up to.
Does Struts offer enough value add to be compelling for use together
with JSF? The list of adds is fairly thin at the moment, and IMHO
this is a way that Struts2 should distinguish itself, by focusing on
this area of development. But that's for the future.
That's kind of what I've been thinking. For me, Tiles is a huge add but
I'm not wedded to ActionForms, etc. I look forward to the controller
imporvements to be discussed on struts-dev!
Thanks for your hard work on both of these projects!
sean
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
