commandButton with window.confirm() and disabled

[designpattern]

I would like to use a commandButtonin combination with the window.confirm() dialog like this:

Code: Select all

        <p:commandButton id="delete"
                         value="#{msgs['button.delete']}"
                         onclick="return confirm('#{msgs.confirm} Categoria Entrata?')"
                         action="#{categorieEntrateForm.delete}"
                         disabled="#{empty categorieEntrateForm.categorieEntrate.idCategoria}"
                         ajax="false" 
                         />

This button does never reach the categorieEntrateForm.delete method.

When I remove the disabled=".." attribute, or replace it by a simple true value, everything works fine. (idCategoria is used to distinguished new and edited records and is null or a long value). The disabled attribute works as expected (button disabled for null values, active for non nulls).

Am I doing something wrong or is this a bug?

(i do not want to use the primefaces confirmDialog, it would be overkill just to ask a simple yes/no question.)
(This worked fine with PF 2.1, I'm upgrading to 2.2.1 and experiencing this problem)

[designpattern]

I found a solution to this problem.

It tourned out that the disabled attribute caused an extra request after the confirm dialog had been shown (btw: not nice).
Since I used request scope only, the value was always null on this request. And PF failed in some way instead of processing the request (not nice).

[kukeltje]

I never use the window.confirm anymore since it does not style with the app. So I never have these (in your terms 'not nice') issues anymore. I Use the http://www.primefaces.org/showcase-labs ... Dialog.jsf