On Jan 17, 2008 4:00 AM, Marko Asplund <[EMAIL PROTECTED]> wrote:
>
> Ryan Wynn wrote:
>
> > see https://issues.apache.org/jira/browse/TOMAHAWK-596
>
>
> Thanks, Ryan.
> Based on the bug report activity there doesn't seem to be any work being
> done to fix this in Tomahawk.
> How did you end up working around the issue?
> Does the patch that's attached to the bug report work correctly?

Marko,

The problem (as least for me) only happens when there is a render
request to a portlet that is currently displaying a view with a
t:dataScroller on it.  In this case the view is restored and for some
reason the transient links for the dataScroller exist in the restored
view.  This becomes a problem during rendering because the links are
then re-added causing duplicate ids.

The patch that I attached to the bug report has worked fine for me.
It basically checks for the existence of those links before adding.  I
have not had any problems since with t:dataScroller on WebSphere
Portal.  You would simply need to override the renderer in
faces-config.xml with the patched version.


Hope this helps,
Ryan


>
> marko
>

Reply via email to