@Jens : We analyzed this issue and looks more like a DLNA CTT issue. I will be creating a bug with them to check if they accept it.

Based on ContentDirectory-v3-Service under Annex C.2.2.9 storageFolder:container: "This class is derived from the container class and inherits the properties defined by that class. Additionally,
the following REQUIRED properties are defined for this class:"

It looks like DLNA CTT is not considering storageFolder

Created attachment 247148 [details] [review]
server,media-export: Use object.container

We used to use object.container.storageFolder for XBox 360 compatibility but
DLNA doesn't like that.

Created attachment 247150 [details] [review]
media-export: Use DLNA-compliant createClass

DLNA does not like upnp:createClass other than object.container for
containers. So we use that and use the possibility to "upgrade" the
object's class upon creation.

(In reply to comment #1)
> @Jens : We analyzed this issue and looks more like a DLNA CTT issue. I will be
> creating a bug with them to check if they accept it.
> 
> Based on ContentDirectory-v3-Service under Annex C.2.2.9
> storageFolder:container: "This class is derived from the container class and
> inherits the properties defined by that class. Additionally,
> the following REQUIRED properties are defined for this class:"
> 
> It looks like DLNA CTT is not considering storageFolder

Please check. It was ok to use though when create-folder caps wasn't involved. But having said that, we only use it for compatibility with the XBox 360's DMP and this can be handled otherwise (patch in comment 2)

Leaving this bug open for now

Attachment 247148 [details] pushed as 56845ce - server,media-export: Use object.container
Attachment 247150 [details] pushed as 92885a0 - media-export: Use DLNA-compliant createClass

@Jens : FYI,I have raised this issue with DLNA. https://dlnadev.org/bugzilla/show_bug.cgi?id=1812

Will let you know what they come up with.

Also https://dlnadev.org/bugzilla/show_bug.cgi?id=1813

sorry, can't access that.

-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rygel/issues/39.