I'm trying to implement an AV Media Server using cling. I could get it working, so that i can see it in the cling workbench (and can browse some directories). Now i tried some (in fact all linux compatible i could find ;) ) clients to check against them. Well, djmount (http://djmount.sourceforge.net/) is the only one working.
I tested with:
Rhythmbox (which shows the server, but due to a bug in the rhythmbox plugin can't browse. It stumbles over clings requirement for correct content-types [see other post here ;)]....)
XBMC (xbox media center, doesnt show the my server at all).
I tried some other media servers (mediatomb and ps3mediaserver), they work fine.
Well, i tried the upnp developer tools (http://opentools.homeip.net/dev-tools-for-upnp). My client doesnt show up in their "device spy". I thought i had an error in my code. So i took the light example from the documentation copied it to the windows box: it doesnt show up neither! (also tried it over the network let the light run on my linux box). They include a similar example, which works with their "device spy" but not with the cling workbench.
I tried to track down the differences using their "device sniffer" (basically displays all ssdp traffic) and wireshark, but can hardly see any difference (that would matter) [http://img207.imageshack.us/img207/7650/screenshotfk.png].... Also the description XML looks almost the same.
I'd need your MediaServer to reproduce your problems with XBMC. You should be able to figure out more with more extensive logging.
About the UPnP Dev Tools - they are no longer supported by Intel and I do not consider them to be a reference at all: When I recently tested them I found quite a few problems and I send bugreports to the developer. Especially the "Network Light" was broken. I can see there is a new version (0.0.41) out now and I'd have to test it again. Please let me know what version you use in future posts.
Just noticed: The cling workbench displays something about the Intel Light:
WARNING - 16:30:15:586 - Thread 26 (Active: 4) : cling.protocol.RetrieveRemoteDescriptors.describe : Could not hydrate device or its services from descriptor: (RemoteDevice) Identity: (RemoteDeviceIdentity, UDN: uuid:c34cbaf7-65a5-4ed1-a022-8f0bb00c2a15), Root: true
WARNING - 16:30:15:587 - Thread 26 (Active: 4) : cling.protocol.RetrieveRemoteDescriptors.describe : Cause was: org.teleal.cling.binding.xml.DescriptorBindingException: Could not parse device descriptor: org.teleal.cling.binding.xml.DescriptorBindingException: Could not parse device DOM: java.lang.RuntimeException: Can't parse Service ID string (namespace/id): urn:upnp-org:serviceId:DimmingService.0001
well ok, the string looks crippled...
Sorry about the versions, you're right, i use the Beta4. But i included the childcount in the didl xml, so this shouldnt cause the problem. I use the newest developer tools v0.0.41.
I took another look at XBMC, and leave the device sniffer running. It never issues a M-Search ssdp request..... Ps3Mediaserver notifys itself every 10 secs! Maybe that's the cause... Well i guess i have to look into cling how to send more notifys... If it doesn't help i'll send you my code :)
This service identifier is indeed valid, I've relaxed the parsing rules in beta5 trunk.
If you are seriously developing with Cling you might want to stay current with a build from SVN source trunk until 1.0 final is done. I'll release new beta versions about once a month only.
If XBMC doesn't send an M-SEARCH multicast it won't find anything immediately. I'm surprised this works at all with other media servers? Well, if you set the maximum age of your LocalDevice in Cling to 10 seconds, you get the same effect and buggy control points are probably the reason why it's such a short timeout in PS3MediaServer. It's not a problem though, your LAN should be able to deal with that traffic :)
I can now see/control the light in the Device Spy. These tools also have debug/log panels and I could see the parsing error of the descriptor in there. Maybe that will help you debug future problems with your MediaServer.