Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Trivial
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Description
Scheduler XML-RPC API return wrong error-message/code. E.g.
UploadPlaylistMethod() returns "missing session ID argument" instead
disapprove wrong datetime parameter. ADDITIONAL INFORMATION: Did not
checked other methods yet, will append similar bugs here.
UploadPlaylistMethod() returns "missing session ID argument" instead
disapprove wrong datetime parameter. ADDITIONAL INFORMATION: Did not
checked other methods yet, will append similar bugs here.
parameter? Are you sure you did have a correct session ID parameter
returned by the login method? Note that a call to resetStorage
invalidates the session ID and you need to log in again.
Here is an example. Following works fine: <methodCall>
<methodName>displaySchedule</methodName> <params> <param>
<value><struct> <member><name>sessionId</name>
<value><string>01b5c29e9ee7fd2735f6aa2d4a8d33c7</string></value>
</member> <member><name>from</name>
<value><dateTime.iso8601>20050227T00:00:00</dateTime.iso8601></value>
</member> <member><name>to</name>
<value><dateTime.iso8601>20050402T23:59:59</dateTime.iso8601></value>
</member> </struct></value> </param> </params> </methodCall>
Following call with malformed %from% parameter report "Error: missing
session ID argument": <methodCall>
<methodName>displaySchedule</methodName> <params> <param>
<value><struct> <member><name>sessionId</name>
<value><string>01b5c29e9ee7fd2735f6aa2d4a8d33c7</string></value>
</member> <member><name>from</name> <value><dateTime.iso8601>2005-02
-27T00:00:00</dateTime.iso8601></value> </member>
<member><name>to</name>
<value><dateTime.iso8601>20050402T23:59:59</dateTime.iso8601></value>
</member> </struct></value> </param> </params> </methodCall>
OK, thanks -- now they should return "invalid argument format". I
couldn't find any way of getting a more descriptive error message out
of our XML-RPC library, sorry.