This is guesswork, but try making both beans session-scoped to see if
that's related to the problem. I don't see how it could, but for
lack of a better suggestion.....
Other things to try would be using the standard components rather than
the tomahawk components.
When all else fails, you'll need to set some breakpoints in
LifeCycleImpl.execute() and find out where things are going wrong, but
that's generally a lot of work.
Actually, the first thing you should try is the latest svn snapshot or
nightly build (or perhaps the 1.1.1RC1 release candidate. There were
more than 64 bugs reported as fixed since 1.1.0.
On 10/3/05, Enrico Nicola Mirco <[EMAIL PROTECTED]> wrote:
> Hi,
> We have a problem with x:commandLink inside x:dataTable: the action doesn't
> work!!
> In other previous posts I read that the data for datatable must be in
> session scope: this is our situation!
> We use the last nightly. This code worked fine until release the 1.1.0.
>
> <x:dataTable id="table1" binding="#{beanPage1.dataTableUsers}"
> value="#{beanSessionArrayList}" var="rowData">
>
>
> <x:column>
> <x:outputText value="#{rowData.name}"/>
> </x:column>
>
> <x:column>
> <x:commandLink action="#{beanPage1.DeleteUser}">
> <x:graphicImage
> url="/Themes/#{sessionScope.userProfile}/row_delete.gif" title="Delete"
> border="0"/>
> </x:commandLink>
> </x:column>
>
>
> </x:dataTable>
>
>
> /* JAVA BACK-BEAN CODE */
> import org.apache.myfaces.component.html.ext.HtmlDataTable;
> public class Page1 {
>
> private HtmlDataTable m_dataTableUsers;
>
> public Page1() {
> }
>
> public HtmlDataTable getDataTableUsers() {
> return m_dataTableUsers;
> }
>
> public void setDataTableUsers(HtmlDataTable dataTableUsers) {
> this.m_dataTableUsers = dataTableUsers;
> }
>
> public String DeleteUser() {
> // some instructions
> return null;
> }
>
> }
>
> Back-bean is in request scope and beanSessionArrayList is an ArrayList in
> session scope, that is cleared and populated in back-bean.
>
> Any suggestions?
>
> Thanks
>
> Nicola
