Closed
Bug 577415
Opened 14 years ago
Closed 14 years ago
Allow positional parameters for XML-RPC
Categories
(Bugzilla :: WebService, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 3.6
People
(Reporter: mkanat, Assigned: mkanat)
Details
Attachments
(1 file, 1 obsolete file)
541 bytes,
patch
|
gregaryh
:
review+
|
Details | Diff | Splinter Review |
The Testopia WebService uses positional parameters, and the XML-RPC in Bugzilla 3.6 doesn't allow this. JSON-RPC will always require positional parameters, but it's possible that we can work around things for 3.6 for XML-RPC.
Assignee | ||
Comment 1•14 years ago
|
||
Okay, does this fix it for you, ghendricks?
Comment 2•14 years ago
|
||
Comment on attachment 456379 [details] [diff] [review] v1 I still get an error but it is coming from Login::CGI: Fault: Client Can't use string ("1") as a HASH ref while "strict refs" in use at Bugzilla/Auth/Login/CGI.pm line 45. Here is my call: $soapresult = $proxy->call('Environment.get_runs', 1);
Comment 3•14 years ago
|
||
Comment on attachment 456379 [details] [diff] [review] v1 + $params = {} if !ref $params eq 'HASH'; should be + $params = {} if ref $params ne 'HASH'; Then it works. :)
Attachment #456379 -
Flags: review?(ghendricks) → review-
Assignee | ||
Comment 4•14 years ago
|
||
Oh right, duh. :-) Thanks!
Attachment #456379 -
Attachment is obsolete: true
Attachment #456473 -
Flags: review?(ghendricks)
Updated•14 years ago
|
Attachment #456473 -
Flags: review?(ghendricks) → review+
Updated•14 years ago
|
Flags: approval?
Assignee | ||
Updated•14 years ago
|
Flags: approval?
Flags: approval4.0+
Flags: approval3.6+
Flags: approval+
Assignee | ||
Comment 5•14 years ago
|
||
Committing to: bzr+ssh://bzr.mozilla.org/bugzilla/trunk/ modified Bugzilla/WebService/Server/XMLRPC.pm Committed revision 7305. Committing to: bzr+ssh://bzr.mozilla.org/bugzilla/4.0/ modified Bugzilla/WebService/Server/XMLRPC.pm Committed revision 7297. Committing to: bzr+ssh://bzr.mozilla.org/bugzilla/3.6/ modified Bugzilla/WebService/Server/XMLRPC.pm Committed revision 7125.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•