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-2969-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? 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. 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? The second patch http://track.sipfoundry.org/secure/attachment/17112/0002-XCF-2969-created-AcmeService-for-demo-purposes.patch contains the example service. This is only important for developers who want to add their own services (We have similar examples for phones and gateways). I'll check it in once the services become more settled: but I would really like to see install it in developers builds only. Ideas? D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
