Any chance that a committer can apply the patch from
https://issues.apache.org/jira/browse/TAP5-1778 somewhere in the upcoming
5.4 release. The issue has the patch, it addresses the problem at hand and
in the worst case scenario has no effect on users who don't care about
this.
Cheers - Alex K
This might be the client-side counterpart of
https://issues.apache.org/jira/browse/TAP5-2075 ?
On 17/04/2014, at 7:08 AM, Balázs Palcsó wrote:
> Hi,
>
> I was trying to apply @AssertTrue on a boolean field.
> I noticed that it is ignored during the server side validation. So I
> implemented cus
Hi,
I was trying to apply @AssertTrue on a boolean field.
I noticed that it is ignored during the server side validation. So I
implemented custom validation on my page in onValidate().
Now I tried to attach a custom client side validation to my field annotated
with @AssertTrue as it is described a
Ah rowClass - I'll check that. Its past midnight and I'm about to retire
for the night.
As for binding to a parameter, I didn't think to do that in the page class.
I've been focussing on the template. Will give it a shot next opportunity.
Thank for the quick suggestions, now I probably won't get
Hi.
Can't you bind the exclude parameter of the grid to a method that excludes
extra columns, if the user is not logged in?
- And i think that you may be looking for rowClass parameter of the grid,
not class.
I would suggest that you take a look at the documentation for the grid...
http://tapest
Hi Tapsters,
I'm converting an old table with a t:Loop component into a t:Grid component.
I used to have a table that hid the username/password columns and now for a
non-admin user with the grid the columns show.
You can see the code below.
Would I have to define the inside a
block to get the
