p:dataTable and p:commandButton with AJAX

[oranheim]

I'm not able to get a p:commandButton to fire my AJAX action in a p:dataTable.

Code: Select all

<p:dataTable ...>
<p:column>
   <p:commandButton style="clear: right;" image="ui-icon ui-icon-arrowreturn-1-w" action="#{messengerService.createResponse}">
      <f:setPropertyActionListener target="#{messengerService.selectedMessageId}" value="1001"></f:setPropertyActionListener>
   </p:commandButton>
</p:column>
</p:dataTable>

I have tried all kinds of combinations: only actionListener, only action, using p:ajax, using p:remoteCommand, etc.

Please advice!

[cagatay.civici]

Does h:datatable work?

[oranheim]

No, it doesn't either and that's why I hoped PrimeFaces to work out.

[cagatay.civici]

Then there is sth wrong with your bean.

[oranheim]

Then there is sth wrong with your bean.

You are right! I made a test case outside my app and there it works.

Thanks for your help

[oranheim]

Then there is sth wrong with your bean.

My issue turns out to be two folded:

1) I passed a request.messageId to by bean, in which was not propogated during the sub-sequent ajax request and caused it to fail. Wrong bean state managmenet.

2) It turns out the new resource aggregator got a bug. It throws an IndexOutOfBoundsException: Index: 0, Size: 0 when you use a ui:fragmenet within a h:head -> f:facet name="first".

I truncate the IndexOutOfBoundsException using Seam Catch, so I'm somewhat fine for now. But, it's a real blocker for Seam 3.1 devs, because of Seam 3.1's Transaction Filter mechanism. Conversely, if you use a ui:fragment in h:head, all Seam Transactions will suffer from being rollbacked.

Hope you can try to reproduce and look into it.

Code: Select all

    <f:facet name="first">    
        <meta content='text/html; charset=UTF-8' http-equiv="Content-Type" />
        <meta name="keywords" content="concert,live music,contract,performance contract,agreement,booking,calendar,performing arts,musific,artist,venue,band,choir,orchestra,manager,stage" />

        <ui:fragment rendered="#{!('/parts/public/profile/profile-view.jsf'.equals(request.requestURI))}">
        <meta name="description" content="Comprehensive on-line services for artists, venues, and professional intermediaries in the live music industry. Enhance the potentials of live music with online booking and contracting." />
        </ui:fragment>

        <ui:fragment rendered="#{'/parts/public/profile/profile-view.jsf'.equals(request.requestURI)}">
        <meta name="description" content="#{unitProfileView.metaDescription}" />
        </ui:fragment>
        <title><h:outputText value="#{bundles.messages['musific.title']}" rendered="#{!'/parts/public/profile/profile-view.jsf'.equals(request.requestURI)}"/><h:outputText value="#{unitProfileView.metaTitle} on Musific" rendered="#{'/parts/public/profile/profile-view.jsf'.equals(request.requestURI)}"/></title>
        <link rel="shortcut icon" href="#{resource['gfx:favicon.ico']}" type="image/x-icon" />
    </f:facet>

[cagatay.civici]

Maybe you should discuss this with your friends at seam-dev chat room, it is always a PrimeFaces bug isn't it?