On Wed, 13 Oct 2004 09:18:53 -0400, Sean Schofield
<[EMAIL PROTECTED]> wrote:
> 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!)
Yes, "rendered" is quite handy. It's standard on all components, and
it's recursive.
With Creator (which has nice support for consuming web services), I
used Google's published API for doing searches via a SOAP request to
build a little demo program -- with the text field for the query
string, and the results table, on the same page. I only wanted to
display the table if there were actually any results ... easy to do:
<h:dataTable ... rendered="#{Search.resultsAvailable}" ...>
...
</h:dataTable>
where Search is my backing bean for the page, and resultsAvailable is
a boolean property indicating whether there are currently any results
ready to be displayed (from the last search). Now, the entire table
is either displayed or not displayed, based on that value.
>
> >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.
>
If you look at how it actually works, it's really a front controller
(JSF) in front of a front controller (Struts), where the outer one is
dealing with user interface events (clicking the node of a tree
control to expand or contract, for example), while the inner one is
dealing with business transactions.
>
> sean
>
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
