Hi Srikanth,

>-----Original Message-----
>From: [email protected] [mailto:qt-mobility-
>[email protected]] On Behalf Of Kyatham Srikanth.1 (Nokia-
>MS/Oulu)

>On the *nix platforms(mobile) it seems that once the descriptionxml is
>placed in a directory, I am able to call QServiceManager::addService().

>After couple of application launches the xml is disappearing and also I
>cannot see the service using servicefw browse.

The SFW does not keep track of the xml file. It is used only once when 
addService() is called. From that point onwards the file is no longer necessary 
as its information was imported into the database. In theory a standard Linux 
package manager would not even have to keep the xml file around on the file 
system. 

In your case I am not even sure who deletes the xml file. The SFW certainly 
does not do such a thing.

With regards to the service disappearing from the database, I cannot think of a 
good reason why this should happen unless somebody calls removeService(). 
Otherwise the entry would indefinitely remain in the database. Do other 
services disappear as well and do they disappear at the same time? It could be 
that somebody deletes the database without you knowing about it (after some 
flash updates, or home dorectory being renewed). The user scope db can be found 
under ~/.config/Nokia and the system scope database under /etc/xdg/Nokia.

Also could you please check whether the database contains your service entries? 
A tool like sqlitebrowser can be pointed to the database file and shows all 
tables and their content. 

Otherwise do you have more detail on how we might be able to reproduce this 
error? I just started a sfw client which uses an installed service. Even after 
10-15 starts the service did not disappear. Then again this was done in an 
environment where I know nobody else in the system is calling removeService().
--
Alex




_______________________________________________
Qt-mobility-feedback mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback

Reply via email to