Prevent duplicate sorcery wizards from being applied to sorcery object types.
authorMark Michelson <mmichelson@digium.com>
Wed, 2 Apr 2014 18:57:29 +0000 (18:57 +0000)
committerMark Michelson <mmichelson@digium.com>
Wed, 2 Apr 2014 18:57:29 +0000 (18:57 +0000)
commiteefcb79bfb4ce2bd0236fc4bb5d960a6df9f3cc4
tree15e35325d8e0cd53f0dae6bfbb987abb84456bc2
parentc704795dcbc5caa5676a1685d6a5996e92875ae9
Prevent duplicate sorcery wizards from being applied to sorcery object types.

This commit contains several changes to sorcery:

1) Application of sorcery configuration based on module name is automatically performed
when sorcery is opened for a module.
2) Sorcery will not attempt to apply the same wizard to an object type more than once.
3) Sorcery gives more exact results when attempting to apply a wizard, whether as the
default or based on configuration.

Sorcery unit tests still pass for me after making these changes.

Review: https://reviewboard.asterisk.org/r/3326
........

Merged revisions 411159 from http://svn.asterisk.org/svn/asterisk/branches/12

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@411656 65c4cc65-6c06-0410-ace0-fbb531ad65f3
configs/sorcery.conf.sample
include/asterisk/sorcery.h
main/bucket.c
main/sorcery.c
res/res_mwi_external.c
res/res_pjsip/config_system.c
res/res_pjsip/pjsip_configuration.c
tests/test_sorcery.c
tests/test_sorcery_astdb.c
tests/test_sorcery_realtime.c