Damian wrote: >http://track.sipfoundry.org/browse/XCF-2969 > >I committed a big part of Bogdan's patch. > >There are just 2 small patches that need to be added to enable >this functionality but I have some questions. > >This patch: >http://track.sipfoundry.org/secure/attachment/17111/0001-XCF-29 >69-created-the-infrastructure-for-plugging-in.patch > >adds all the services that are not found yet to the DB. > >If we are going to do it this way should we still add the >service definition in DB patches?
Not sure what you mean here by DB patches? Can you explain? >Is it OK if I move the call to 'searchForNewServices' to >FirstRunTask: that would mean that if someone installs a new >service they would need to run: > > sipxconfig.sh --first-run > >to make it manageable. > I think that's reasonable. >And since we are on the subject: why would we even try to add >the service to the DB until it's actually added to at lead one >of the servers? If we always get the list of potential >services from beans definitions that there is not need for DB >patches or 'searchForNewServices' method. Anybody sees >problems with changing it? > In my particular case, I need the 3rd party service to come up automatically on the master system. It probably wouldn't be acceptable to the Administrator to have to go into the Services and manually add it in order to get his sytem running properly. Raymond _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
