sorcery: Don't try to load object types which haven't been defined.
authorJoshua Colp <jcolp@digium.com>
Wed, 4 Feb 2015 00:59:14 +0000 (00:59 +0000)
committerJoshua Colp <jcolp@digium.com>
Wed, 4 Feb 2015 00:59:14 +0000 (00:59 +0000)
commit03ce56d6c5e35fa170c9af2c4aaa0fa05e58be4e
tree345bc3d0c8632af5f95c653f4ba10068211350f1
parent14a57782a6685a4fb432e18527974188b3f76ecf
sorcery: Don't try to load object types which haven't been defined.

The act of defining wizards for an object type in sorcery.conf will
create a minimal object type. This can cause a problem when a module
has multiple sorcery instances (which all get the wizards from sorcery.conf
applied) but the sorcery instances do not all contain full information
about the object types. Upon loading errors will occur stating that
the objects can not be created. This is confusing and is actually
perfectly fine.

This change makes it so that only object types which have been fully
defined will be loaded.

ASTERISK-24748 #close
Reported by: Joshua Colp
........

Merged revisions 431538 from http://svn.asterisk.org/svn/asterisk/branches/13

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@431539 65c4cc65-6c06-0410-ace0-fbb531ad65f3
main/sorcery.c