footh pisze: > I am contemplating migrating to Cocoon 2.2. My main > application has a couple sub-applications (with > separate sitemaps) and one of those sub-apps in turn > has a sub-application. > > My question is: do I deal with the sub-apps by > creating blocks for each one? The problem is, these > sub-applications have forms, which I understand should > be separated out into a block. So, if I have four > sub-apps all with forms, then it seems I will have > eight blocks to deal with. And that's only if I use > two blocks for each sub-app.
Why do you want to have forms for each of your block in separate blocks? How you made an assumption that is needed? Blocks are used mainly as packaging units for different applications or reusable pieces of functionality. It makes sense to put your applications into separate block because it is a complete unit that should be separated from other applications. If forms you mentioned are application-specific then there is no point to extract them into separate block. > I guess I am confused as to exactly how I'm supposed > to architect a full web-app under the new 2.2 > paradigm. I learned Cocoon 2.1 by pouring through the > samples but I can't seem to find similar samples in > 2.2 as everything appears to work through Maven. > > Can anyone offer help or point me in the right > direction? (I've read all the 2.2 tutorials). I couldn't give you more concrete advice without knowing more about your applications. If you want further explanations I'm happy to help as long as you provide more details. Also sorry for my late response. -- Grzegorz Kossakowski Committer and PMC Member of Apache Cocoon http://reflectingonthevicissitudes.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
