james-gibson

Main Thread (Suspended: TypeError: Error #1034: Type Coercion failed: cannot convert mx.rpc::Fault@bf8e3c1 to mx.rpc.events.FaultEvent.)	
	mx.rpc::AsyncResponder/fault	
	com.esri.ags.tasks::BaseTask/handleError	
	com.esri.ags.tasks::BaseTask/handleResult	
	Function/com.esri.ags.tasks:BaseTask/esri_internal:sendURLVariables2/com.esri.ags.tasks:result	
	mx.rpc::Responder/result	
	mx.rpc::AsyncToken/http://www.adobe.com/2006/flex/mx/internal::applyResult	
	mx.rpc.events::ResultEvent/http://www.adobe.com/2006/flex/mx/internal::callTokenResponders	
	HTTPOperation/http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent	
	mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::resultHandler	

james-gibson

<amcharts:AmGraph 
				id="icGraph" 
				fillAlphas="[1]" 
				fillColors="[mbtuUsageColor]"
				lineAlpha="0" 
				title="" 
				type="column"
				valueAxis="{contributionAxis}"
				valueField="percentOfInstallationMbtuUsage"
				/>

james-gibson

<amcharts:AmGraph 
				id="icGraph" 
				fillAlphas="[1]" 
				fillColors="[mbtuUsageColor]"
				lineAlpha="0" 
				title="" 
				type="column"
				valueAxis="{contributionAxis}"
				valueField="percentOfInstallationMbtuUsage"
				/>

james-gibson

My colleagues and I are working to develop a more robust domain model for an application we are working on. The core entities that we are working with are "World", "Region", "Installation", and "Facility". The relationship to one another can be drawn as:

![enter image description here][1]

This means that our World object contains a collection of Regions, the Region object contains a collection of Installations, and the Installation object contains a collection of Facilities. This can be modeled as such:

![enter image description here][2]

With this design each collection is responsible for loading the appropriate objects. This includes executing an web service to obtain the proper objects. The owner of each collection is responsible for telling its collection when load itself. For instance: