Farr, Aaron wrote:
If there were a way to specify component startup order, or priority, that would help a lot.
Basically I agree with Nicols point oif view here
me too..
- however - I just want to throw in something that has been bugging me and may help address some aspects of your issue. Currently in merlin the block is parsed relative to types of children - i.e. get all of the compoennt build the metadata, get all of the subcontainers, build their metadata, get all of includes, build the meta data. A better approach would be to process metadata creation exactly in the order declared in the block.xml. This would result in a more predictable ordering of component deployment.
+1 as a good place to start... I've got a situation right now along these lines that is really bugging me. Trying to reuse the hsqldb-component and the cornerstone-datasources component in a merlin container. The hsqldb MUST start before the datasource component... very tricky with merlin... at least with phoenix there was a somewhat predictable pattern.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
