I am working on a small project for which i adopted most of the classes from the AppSkeleton demo.
But there seems to be a problem with the StartupMonitorProxy class.
Here is how to reproduce it.
Add a non-blocking proxy (Proxy1) and at least one more (blocking or non-blocking) proxy (Proxy2-ProxyN) after that.
Start the loading process.
StartupMonitorProxy will now start loading Proxy1 and at least Proxy2.
As soon as Proxy2 has finished it will loop through the chain again and find the first proxy that has not signaled successful loading yet.
In my case, that is Proxy1, so it will try to load it again even though the loading process is still running.
I am aware that this can easily be fixed with an additional flag in the ResourceVO class (among other possible fixes), but as i didn't find this mentioned on the forum i thought i should write a little note