Richard, Sorry, but this won't work and is not intended to work (I discussed this with Ovidiu some months ago). He told me to think the other way around - the flow should be your ONLY controller and decides which page will be sended to the client.
Up to now I didn't run into this problem again but may be you come up with a use case where it is not possible to solve a problem this way please let us know! Regards, Reinhard > -----Original Message----- > From: Richard In Public [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 27, 2003 6:00 PM > To: [EMAIL PROTECTED] > Subject: Continuations in Aggregations? > > > [I originally posted this to cocoon-users but am reposting it > after receiving a suggestion to post it here...] > > > Hi > > I've started (trying) to incorporate FlowScripts/XmlForms > into a project. I'm working from the PetStore example (thanks > Upayavira) and have a paired-down version of the new account form. > > This form is served correctly when access directly > (..cocoon/myproj/newAccountForm.do) but causes the following > exception when access from within an aggregate element: > > org.apache.cocoon.ProcessingException: Attempted to process > incomplete pipeline. > > The relevant parts of my sitemap are below, together with the > full stack trace. > > I sure hope that aggregation and continuations are compatible! > > Thank you, > > Richard Hoberman
