{"action":"created","issue":{"url":"https://api.github.com/repos/52North/sensorweb-rest-api/issues/158","repository_url":"https://api.github.com/repos/52North/sensorweb-rest-api","labels_url":"https://api.github.com/repos/52North/sensorweb-rest-api/issues/158/labels{/name}","comments_url":"https://api.github.com/repos/52North/sensorweb-rest-api/issues/158/comments","events_url":"https://api.github.com/repos/52North/sensorweb-rest-api/issues/158/events","html_url":"https://github.com/52North/sensorweb-rest-api/issues/158","id":133251917,"number":158,"title":"SOS instances management","user":{"login":"zbodrosk","id":1454239,"avatar_url":"https://avatars.githubusercontent.com/u/1454239?v=3","gravatar_id":"","url":"https://api.github.com/users/zbodrosk","html_url":"https://github.com/zbodrosk","followers_url":"https://api.github.com/users/zbodrosk/followers","following_url":"https://api.github.com/users/zbodrosk/following{/other_user}","gists_url":"https://api.github.com/users/zbodrosk/gists{/gist_id}","starred_url":"https://api.github.com/users/zbodrosk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zbodrosk/subscriptions","organizations_url":"https://api.github.com/users/zbodrosk/orgs","repos_url":"https://api.github.com/users/zbodrosk/repos","events_url":"https://api.github.com/users/zbodrosk/events{/privacy}","received_events_url":"https://api.github.com/users/zbodrosk/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-02-12T14:14:01Z","updated_at":"2016-04-22T13:58:50Z","closed_at":null,"body":"(this issue could be also related to [restful-timeseries-proxy](https://github.com/52North/restful-timeseries-proxy) project)\r\n\r\nIs there a feature that would allow dynamic SOS instances adding? I'm aware that similar process could manually be done by editing sos-instances.data.xml in the restful-timeseries-proxy, but what I want is to do the same by the service call without the need to redeploy and to cache all the other SOS instances again.\r\n\r\nIf there is an easier or better way to manage custom SOS instances, I'm open for suggestions.\r\n\r\nIt seems that similar problem has already been addressed here #111 "},"comment":{"url":"https://api.github.com/repos/52North/sensorweb-rest-api/issues/comments/213439694","html_url":"https://github.com/52North/sensorweb-rest-api/issues/158#issuecomment-213439694","issue_url":"https://api.github.com/repos/52North/sensorweb-rest-api/issues/158","id":213439694,"user":{"login":"zbodrosk","id":1454239,"avatar_url":"https://avatars.githubusercontent.com/u/1454239?v=3","gravatar_id":"","url":"https://api.github.com/users/zbodrosk","html_url":"https://github.com/zbodrosk","followers_url":"https://api.github.com/users/zbodrosk/followers","following_url":"https://api.github.com/users/zbodrosk/following{/other_user}","gists_url":"https://api.github.com/users/zbodrosk/gists{/gist_id}","starred_url":"https://api.github.com/users/zbodrosk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zbodrosk/subscriptions","organizations_url":"https://api.github.com/users/zbodrosk/orgs","repos_url":"https://api.github.com/users/zbodrosk/repos","events_url":"https://api.github.com/users/zbodrosk/events{/privacy}","received_events_url":"https://api.github.com/users/zbodrosk/received_events","type":"User","site_admin":false},"created_at":"2016-04-22T13:58:50Z","updated_at":"2016-04-22T13:58:50Z","body":"@ridoo \r\nSorry for late reply.\r\nIn the meantime, as you suggested, we developed feature that reads SOS URLs from the other sources, validates them, and write changes into the `sos-instances.data.xml`.\r\n\r\nBut, there is a problem with this approach. All changes made in the `sos-instance.data.xml` during a runtime will not be persistent after re-deploy. Of course, it's possible (but not convenient)  to write directly into the war file, but that will automatically trigger a re-deploy.\r\n\r\nWe could suggest a few solutions to overcome this problem, but we are not sure is it a right direction to go. In general, if we want to update metadata list during a runtime, content of the `sos-instance.data.xml` should be saved separate from deployment structure. Otherwise, if we want to save existing code structure, it is also possible to maintain that data separately from `sos-instance.data.xml`.  \r\n\r\nPlease, give us your opinion and suggestions. "}}