[asterisk-bugs] [Asterisk 0011086]: avoid nonexistent context warnings when loading AEL

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11086 
====================================================================== 
Reported By:                dimas
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   11086
Category:                   PBX/pbx_ael
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.13  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-25-2007 11:25 CDT
Last Modified:              10-25-2007 17:15 CDT
====================================================================== 
Summary:                    avoid nonexistent context warnings when loading AEL
Description: 
When AEL loads its configuration, it produces alot of warnings like

[Oct 25 19:59:26] WARNING[2457] pbx.c: Context 'FOO' tries includes
nonexistent context 'BAR'

This happens because BAR context is defined later than FOO context. When
you have really many context, they are most likely spread across multiple
files and it is not always possible to organize files in a way that
included context are always loaded before including ones.
====================================================================== 

---------------------------------------------------------------------- 
 murf - 10-25-07 17:15  
---------------------------------------------------------------------- 
This cannot be. The code for the includes check runs after the whole
fileset has been read in, and it searches thru all the contexts that have
been defined. I just wrote up a little test and this works fine.
context Foo
{
        includes
        {
                bar1;
        }
        102 => NoOp(b);
}

context bar1
{
        101 => NoOp(a);
}


Please attach the offending extensions.ael file, and we'll see what the
real 
problem is. My first guess is that you are trying to include an empty
context; empty contexts are ignored by AEL. If you really need to get rid
of the warning, then put some nonsense extension in the empty context.

Another guess is that the context you are including is in extensions.conf;
this will generate a warning, because at load time, AEL is usually loaded
first, and the data will not be available to check. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-25-07 17:15  murf           Note Added: 0072523                          
======================================================================