enabledOnUserRole attribute and Clay
Perhaps I'm overlooking something here, but from the testing I did this
afternoon, it appears that the enabledOnUserRole attribute provided with most
of Tomahawk's components doesn't work at all in Clay HTML templates. However,
it does work properly when I
Perhaps I'm overlooking something here, but from the testing I did this
afternoon, it appears that the enabledOnUserRole attribute provided with
most
of Tomahawk's components doesn't work at all in Clay HTML templates. However,
it does work properly when I use straight JSP/JSF without Clay
@shale.apache.org
Subject: Re: Tomahawk's enabledOnUserRole attribute and Clay
Perhaps I'm overlooking something here, but from the testing I did this
afternoon, it appears that the enabledOnUserRole attribute provided with
most
of Tomahawk's components doesn't work at all in Clay HTML templates. However
: Tomahawk's enabledOnUserRole attribute and Clay
Perhaps I'm overlooking something here, but from the testing I did this
afternoon, it appears that the enabledOnUserRole attribute provided with
most
of Tomahawk's components doesn't work at all in Clay HTML templates.
However,
it does work
the various
library configs for the stateful converters, validators and listeners.
Hermod
Gary
-Opprinnelig melding-
Fra: Gary VanMatre [mailto:[EMAIL PROTECTED]
Sendt: 27. mars 2007 17:06
Til: user@shale.apache.org
Emne: Re: Tomahawk's enabledOnUserRole attribute and Clay
Gary, I see this as a tomahawk bug. I'm pretty sure I looked at this
a couple weeks ago and noticed that the renderer was being set inside
the JSP tag handler rather than in the component. Seems like setting
it from the taghandler is the wrong approach. Breaks anything other
than the jsp
Yes, I brought it up on the myfaces dev list, but didn't get any
comments. I guess I'll open a JIRA issue and take a look at it the
next time I have the code checked out. I don't think we have any
instances of a new tag handler but not a new component subclass.
Yes, the tenative plan is that
I've opened http://issues.apache.org/jira/browse/TOMAHAWK-942 on this.
On 3/27/07, Gary VanMatre [EMAIL PROTECTED] wrote:
From: Mike Kienenberger [EMAIL PROTECTED]
Gary, I see this as a tomahawk bug. I'm pretty sure I looked at this
a couple weeks ago and noticed that the renderer was being
Perhaps I'm overlooking something here, but from the testing I did this
afternoon, it appears that the enabledOnUserRole attribute provided with most
of Tomahawk's components doesn't work at all in Clay HTML templates. However,
it does work properly when I use straight JSP/JSF without Clay (at
