Thanks for the assessment Mike. Fortunately I did just finish converting
the last few pages of my application to facelets, so hopefully I'll have
time to give it a shot next week. I'm going to spend the next half hour
or so looking into this issue, for starters.
This is not a huge thing, but it's really the only thing that "broke"
when switching to facelets. So I'd really like to knock it off.
Mike Kienenberger wrote:
> Jeff,
>
> This is really straight-forward stuff. Two hours should be more than
> sufficient.
> I'd guess it'd take about 5 minutes to cut&paste a similar
> getter/setter pair, then replace the attribute name with the new
> attribute name.
>
> The less-obvious part is going to be going into the renderer and
> changing the references to the generic attribute (map entry) into a
> concrete method call.
>
> The longest part is going to be testing the changes.
>
> On 2/15/07, Jeff Bischoff <[EMAIL PROTECTED]> wrote:
>> (I've moved this thread to the myfaces-users list, due to it being
>> identified as a Tomahawk bug)
>>
>> Heh, Mike do you ever get tired of answering my questions? ;)
>>
>> I looked through MyFaces JIRA, and the closest issue I found was
>> TOMAHAWK-523. The only difference is that they were trying to use EL
>> based off the "var" attribute, whereas I am attempting to use the
>> "rowIndexVar". However, this might be the same issue.
>>
>> That issue is marked "patch available", but there are no files attached.
>> I see that one of your comments on the thread indicates that the patch
>> provided wasn't sufficient... There were also user comments there about
>> it affecting non-facelets, or being fixed in the trunk - both statements
>> which are definately not true for my issue.
>>
>> How involved do you think the fix for this would be? Could it be coded
>> in a couple of hours? Should I attempt to write a patch to fix this?
>>
>> [1] http://issues.apache.org/jira/browse/TOMAHAWK-523
>>
>> Mike Kienenberger wrote:
>> > I think there are already bug reports open on this for Tomahawk, but
>> > you should make sure that this is the case, opening one if necessary.
>> >
>> > My guess it that the jsp tag handler for t:dataTable is not using
>> > standard pass-through code to initialize the rowStyleClass attribute
>> > on the t:dataTable component.
>> >
>> > The fix would be to rewrite the component and tag handler so that the
>> > tag handler isn't doing anything beyond passing the arguments through
>> > unchanged.
>> >
>> > On 2/15/07, Jeff Bischoff <[EMAIL PROTECTED]> wrote:
>> >> Greetings,
>> >>
>> >> There is a CSS trick with the Tomahawk extended dataTable that allows
>> >> the selected row to be highlighted (or some similar things). It works
>> >> great in JSP, and has been passed around on the myfaces mailing
>> list and
>> >> wiki for some time. The trick goes something like this:
>> >>
>> >> <t:dataTable id="TheDataTable"
>> >> ...
>> >> rowClasses="oddRow,evenRow"
>> >> rowStyleClass="#{dataTableBacking.selectedRowIndex == rowIndex ?
>> >> 'highlightRow' : null}"
>> >> rowIndexVar="rowIndex"
>> >> .../>
>> >>
>> >> Unfortunately, when I recently converted my application from JSP to
>> >> Facelets, this trick no longer works. (Fortunately, this is one
of the
>> >> only things that stopped working!) I have heard from other users on
>> the
>> >> myfaces mailing list who also can't get this to work under facelets.
>> >> Apparently, the "rowIndex" variable that t:dataTable creates can't be
>> >> resolved in the rowStyleClass expression, even though it works for
>> >> components who are children of the table.
>> >>
>> >> Any idea why this would be different under Facelets? I am thinking of
>> >> opening a JIRA issue on myfaces project, since this is their custom
>> >> component, but wanted to bounce for ideas here first. Any suggested
>> >> workarounds?
>> >>
>> >> Regards,
>> >>
>> >> Jeff Bischoff
>> >> Kenneth L Kurz & Associates, Inc.
>> >>
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>
>> >>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> >
>> >
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
