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 ${...} A
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" a
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/disp
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
I'm building "dashboard" page that has a bunch of tables on it.
Everything was working nicely until I added one more.
I get a very strange error: [vsm] WARN [btpool0-2] LookupUtil.
(99) | Exception: [.LookupUtil] Error looking up property "username"
in object type "com.versature.vsm.model.Ti
