<is_empty_asset> = true, while there is a valid, usable mediafile

[Michiel.Schok]

When the following procedure is followed, the situation arises that there is an asset with one mediafile, which has a <uri> defined, rather than a mediafile.
The asset has <is_empty_asset> defined as TRUE, but it should be FALSE.

Procedure:

1. create an asset
[post] /asset/create 
user_id=foo

2. create a mediafile
[post] /mediafile/create
user_id=foo
asset_id={id}

3. request an uploadticket
[get] /mediafile/{id}/uploadticket/create?user_id=foo

4. update mediafile
[post] /mediafile/{id}
user_id=foo
uri=http://empty.asset.demo

When issuing an /asset/{id} call:

[GET] asset/{id}
...
<is_empty_asset>TRUE</is_empty_asset>
...

Workaround is available:
Delete the empty mediafile, and create a new one, immediately specifying the URI.

[forgacs]

Ready.

[Michiel.Schok]

When following the script above, an error occurs at step 2: creating the mediafile.
My XML-parser crashes on the response, possibly an empty response with an error 500 - Internal Server Error.

[robert]

review for 2.1 release

[Michiel.Schok]

is_empty_asset is now 'FALSE'