You can do it either way.
I usually do things a bit differently and have one proxy handle the loading and parsing of of the XML itself. I generally use the StartupManager utility and that way if a Proxy later needs the XML that was loaded previously in another Proxy I can ensure it's ready by making it a requirement. I load a ConfigProxy that has all the XML URL's first, then have each loaderProxy call that Proxy internally to get the URL it is responsible for to start loading and parsing.
In this kind of set-up, the flow goes something like this...
(All this is done using the StartupManagerUtility)
- Load config with urls and expose ConfigVo
- DataXMLProxy1 requests configVO and parses XML... exposing it's VO
- DataXMLProxy2 requests configVO and parses XML... exposing it's VO
- DataProxyFinal has a requirement of both 1 & 2 being completed before executing
- DataProxyFinal runs and asks for DataXMLProxy1 VO and DataXMLProxy2 VO
- once it's done StartupManager executes the LoadComplete.
Hope that makes sense, I'm not the greatest at explaining processes