f:setPropertyActionListener indicate double call

[lyahim]

Hello All,

When I use f:setPropertyActionListener inside b:commandButton then action method is called twice. The setter method is called only once, that is indicated by f:setPropertyActionListener.
I checked it only with b:dataTable.
The full code:

<b:dataTable... >
  <h:form >
    <b:commandButton action="..." >
      <f:setPropertyActionListener .../ >
    </b:commandButton >
...

This issue exists with ajax and normal requests too.
Please check it.

Thanks,
Mihaly

[lyahim]

When I tried to make a workaround use actionListener and action combination.

<b:commandButton action="..." actionListener="#{setter(value)}" ...>

Both the action method and the setter method called twice.

Mihaly

[stephanrauh]

Two questions:

• That sounds like a non-AJAX call?
• Is the command button inside the datatable? Or is it below?

[lyahim]

1. The AJAX and non-AJAX call work similar.
2. Yes, there are a delete button on each rows end.

[lyahim]

I paste a code what work with h:commandbutton:

<h:form>
<b:dataTable>
 <h:column>
                        <f:facet name="header">
                            <h:outputText value="" />
                        </f:facet>
                        <h:commandButton 
                        action="..." styleClass="btn btn-default">
                            <f:setPropertyActionListener  />
                            <p:ajax update="@form" />
                        </h:commandButton>
                    </h:column>

</b:dataTable>
<h:form>

[stephanrauh]

Thanks! I'll have a look at the problem later.

BTW, you don't need to separate the < from the tag when you're commenting. Just add ```xml before your source code, and you've got a nice source code formatting and less work. See https://guides.github.com/features/mastering-markdown/ (and browse for "code").

[lyahim]

Thanks, I tried, but with only simple quote mark.

[stephanrauh]

The single backward quote is for inline code. The three quote are for multiline code.

[stephanrauh]

I've fixed the bug and uploaded a developer snapshot to Maven Central. See #151 on how to get it.