On Jun 5, 2007, at 10:38, Matt Raible wrote:
On 6/5/07, Adam Sherman <[EMAIL PROTECTED]> wrote:
On Jun 5, 2007, at 9:43, Matt Raible wrote:
> In some tables, you're using name="..." vs. name="${...}" in some
> other tables. I'd recommend you try to be consistent. You
shouldn't
> need ${...} AFAIK. If that doesn't help, try adding a "uid"
attribute.
>
>> From http://displaytag.sourceforge.net/11/displaytag/
>> tagreference.html:
>
> uid Unique id used to identify this table. The object
representing
> the current row is also added to the pageContext under this
name, so
> that you can refer to it in column bodies using ${uid}. You can
also
> use uid_rowNum to refer to the current row number. Two tables in
the
> same page can't have the same id (paging and sorting will affect
> both). If no "htmlId" is specified the same value will be used
for the
> html id of the generated table.
Indeed, changing id to uid fixed the problem. I just noticed that id
can't take EL before I read your response. :-) I notice that uid
seems to generate an id attribute on the output, so I don't need to
use id at all, right?
Correct.
As I get further into this, I'm hitting a snag: if I dynamically
generate the value for the "uid" attribute, I can't access the
current row in a property tag. I'm iterating over a Collection of
Domain objects, creating a table for the Domain.accounts Collection.
Since each table needs to have a unique "uid" attribute, I'm opening
it like so:
<display:table name="${domain.accounts}" uid="${domain.domain}
AccountList">
But then I can't use the body of the property tag to format the
field. Any ideas?
Maybe there is a way to achieve this using grouping that would be
simpler?
Thanks again,
A.
--
Adam Sherman
Technologist
+1 (613) 797-6819 | http://www.sherman.ca/ | sip:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
