On update URI::InvalidURIError: URI must be ascii only

[luckyraul]

conn = OData::Service.new "same_ip/hamster/odata/standard.odata"
conn.Document_СчетНаОплатуПокупателю
results = conn.execute
doc = results.first
doc.Комментарий = 'ruby update'

conn.update_object(doc)
result = conn.save_changes
puts "Was updated? #{result}"

[visoft]

Try the develop branch. I believe I fixed this.

[luckyraul]

Uri error is gone, however

OData::ServiceError: XML parsing error:  - [1,1]
Fatal error: 
Document is empty

[visoft]

I got that too, I figured I didn't have access to update your entities.

I'll look into this.

[luckyraul]

What was the server answer? This service is not our application, just some vendor server software, so there can be some restrictions on editing, which I can't predict. If you find some restrictions responses - I can look in configuration.

[visoft]

Here's the raw error:

<m:error xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
  <m:code>-1</m:code>
  <m:message>XML parsing error:  - [1,1]
Fatal error: 
Document is empty
</m:message>
</m:error>

I can confirm the document is being sent over as JSON to the server with the proper Content-Type of application/json. ruby_odata receives XML and sends JSON, so I wonder if your server doesn't support JSON given that it looks like it's trying to parse XML?

[luckyraul]

Yeah. As far as I am concerned it does not support json yet.

[luckyraul]

I updated service. So It you want json answer you should request with header Accept: application/json or parameter ?$format=json in query mode.

[luckyraul]

I dumped http and found that library use always "accept xml"

[visoft]

Yes, it always accepts XML, but when it sends out say an update, it's content-type is set to application/json

[visoft]

ruby_odata doesn't want JSON back (Accept) otherwise I'd have to have 2 different parsers

[luckyraul]

here said to use PATCH method http://www.odata.org/getting-started/basic-tutorial/

[visoft]

The OData services SHOULD support PATCH as the preferred means of updating an entity. But also services MAY additionally support PUT.

ruby_odata uses a PUT to send over the updates since it's updating the whole entity, not just pieces of it (which is what PATCHshould be used for).

[luckyraul]

I've checked my issue and added ?$format=json to url and got error answer

{
"odata.error": {
"code": "4",
"message": {
"lang": "ru",
"value": "ВозвратнаяТара"
}
}