Hi, all. I've been reading documentation and poking around the sample bundle for a few days now, and it seems like Cocoon should be a suitable framework for my current project. I'm in research/proof-of-concept mode ATM though, and have just found that the design I had in mind is probably not going to work. I wanted to provide a few reusable resources that returned XML data, and let my administrator reference them in the sitemap as necessary. Some of those resources may require user input, and I thought I'd use flow/continuations for that. E.g.,
<!-- provide reusable data access / collection mechanisms --> Pipeline 1: Get some data from a database and represent result as XML Pipeline 2: Present the user with some series of forms, do stuff, and represent result as XML Pipeline 3: Present the user with some other forms, do other stuff, and represent result as XML <!-- and reference them --> Pipeline 4: get xml result from pipeline 2 Pipeline 5: get xml result from pipelines 1 and 2 Pipeline 6: get xml result from pipelines 2 and 3 The idea is that the flowscripts themselves don't know anything about which resource should be called next... Am I barking up the wrong tree here? Can I 'aggregate' flow results, or is this just bad design? Alternative approaches or references to additional documentation are much appreciated. TIA, Bill --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
