[erlang-questions] Distributed Applications: Stop Before Start?

Vance Shipley <>
Thu Mar 29 06:50:52 CEST 2012


On Wed, Mar 28, 2012 at 02:04:10PM +0100, Tim Watson wrote:
}  On 28 March 2012 12:40, Vance Shipley <> wrote:
}  > /Users/otpuser/lib/erlang/doc/design_principles/included_applications.html
}  >
}  >  "This means that when running, an included application is in fact part
}  >   of the primary application and a process in an included application
}  >   will consider itself belonging to the primary application."
}  >
}  > So if a process in the snmp application would call application:get_all_env/0
}  > it wouldn't get what it expects.  It does look like all the calls to the
}  > application module do include the application name (snmp) however.
}  
}  Is calling application:load(snmp) prior to starting the top level
}  supervisor the 'right way' to resolve this issue when working with
}  included_applications?

No, loading the application doesn't help.  It's loaded anyway by virtue
of being listed in the included_applications key of the application resource
file.

-- 
	-Vance



More information about the erlang-questions mailing list