Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Received-SPF: pass (nike.apache.org: domain of lu4242@gmail.com designates
 209.85.160.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4FF295CD.403@his.de>
References: <4FED6DA2.1060308@his.de>
	<CABujnVcSv3nX33cxCsT7+yXo5xmcCY49ej=VYUd-u=tvWe2e7A@mail.gmail.com>
	<4FF295CD.403@his.de>
Date: Wed, 4 Jul 2012 09:52:02 +0200
Message-ID: 
 <CABujnVfzTr5t-8OD2hp1oxGKRuGEaPatM4JFS0_sh56XX9YEvQ@mail.gmail.com>
Subject: Re: disabled <f:ajax /> not working (?)
From: Leonardo Uribe <lu4242@gmail.com>
To: MyFaces Development <dev@myfaces.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi

I have been thinking about it, and look the issue from other point of
view is valid too. I have an ajax button, and I disable the ajax
behavior, why the button should magically "convert" into a normal
submit button. Also, there are considerations from performance
perspective, because that means we should evaluate disable property
for every client behavior before call the submit script code, so at
the end we should evaluate twice that attribute, one to check and the
second one to render the script.

After the previous considerations, it sounds better let it as is.

regards,

Leonardo Uribe

2012/7/3 Dennis H=F6rsch <hoersch@his.de>:
> Hi
>
> So, what to do next? Should I make a ticket at MyFaces?
>
> Greetings,
> dennis
>
> Am 29.06.2012 15:12, schrieb Leonardo Uribe:
>
>> Hi
>>
>> Probably that's something not explicitly specified, but I think at
>> first view it has sense what you say. If the client behavior is
>> disabled, it should not generate any scripts, and the submit should
>> work as usual.
>>
>> regards,
>>
>> Leonardo Uribe
>>
>> 2012/6/29 Dennis H=F6rsch<hoersch@his.de>:
>>>
>>> Hi,
>>>
>>> I tested to disable all<f:ajax />  temporally on my page
>>> (programatically,
>>> for testing reasons).
>>> The behavior that I would expect is that the button then submits as
>>> without
>>> the f:ajax tag.
>>>
>>> But instead of this, the whole button is kind of disabled. This is also
>>> the
>>> case if I disable the f:ajax directly:
>>> <h:commandButton value=3D"Show">
>>> <f:ajax execute=3D"@this" render=3D"@form" disabled=3D"true" />
>>> <f:setPropertyActionListener target=3D"#{flash.show}" value=3D"true" />
>>> </h:commandButton>
>>>
>>> In the HTML the button has an onclick with 'return false'. Is this the
>>> desired  behavior?
>>> As I discovered so far this 'return false' is in the end depend on
>>> AjaxBehavior.getHints().
>>>
>>> "getHints(): This method returns an unmodifiable Set containing the
>>> ClientBehaviorHint SUBMITTING."
>>>
>>> (http://javaserverfaces.java.net/nonav/docs/2.1/javadocs/javax/faces/co=
mponent/behavior/AjaxBehavior.html)
>>>
>>> But why does the AjaxBehavior pretend to be 'SUBMITTING' while generati=
ng
>>> no
>>> script?
>>>
>>> If I change it to return an empty set if it is disabled it works as
>>> expected.
>>>
>>> Greetings
>>> dennis
>>>
>>> --
>>> HIS Hochschul-Informations-System GmbH
>>> Goseriede 9 | 30159 Hannover |www.his.de
>>>
>>> Dennis H=F6rsch
>>> Unternehmensbereich Hochschul-IT
>>> Arbeitsbereich Personalmanagement
>>> Telefon +49 (0)511 1220-403
>>> E-Mailhoersch@his.de
>>>
>>> Registergericht: Amtsgericht Hannover, HRB 6489
>>> Gesch=E4ftsf=FChrer: Prof. Dr. Martin Leitner
>>> Vorsitzender des Aufsichtsrats: Prof. Dr. Andreas Geiger
>>>
>>>
>
>