fireAjax first argument and the name=value pairs sent to the server

[glassfishrobot]

On Tue, 17 Apr 2007 13:57:29 -0700, Matthew Bohm Matthew.Bohm@Sun.COM said:

MB> I've remembered an important technical question: when MB> DynaFaces.fireAjaxTransaction(this,

{inputs: form1:textField1, render: MB> form1:staticText1}

) is invoked upon clicking a button, by passing "this" MB> should the button information be sent in the request, even though it is MB> not specified in the inputs? Currently, without specifying the button MB> among the inputs, the button information is not sent in the request. I'm MB> not sure if this is a bug.

MB> I would have to consider it a bug. Ironically, it is a bug with at least MB> one quasi-benefit to my AjaxTransaction component: by forcing you to MB> specify the button as one of the inputs, the button is necessarily MB> color-coded in the designer, which is visually helpful. Even if/when we MB> fix this, I would want to make sure that specifying the button MB> explicitly among the inputs does not do harm at runtime. By providing MB> users the option of specifying the button explicitly among the inputs, MB> they can continue to gain the visual benefit at designtime.

Environment

Operating System: All Platform: Sun

Affected Versions

[current]

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/jsf-extensions/issues/70
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @glassfishrobot

[glassfishrobot]

@glassfishrobot Commented Reported by @edburns

[glassfishrobot]

@glassfishrobot Commented Was assigned to jsf-extensions-issues

[glassfishrobot]

@glassfishrobot Commented This issue was imported from java.net JIRA JSF_EXTENSIONS-70