Do you mean just plain web application? It's Struts' territory :) Seriously, Cocoon has a steep learning curve. So, it's hard to "sell" it, unless there's something special in the webapp, imho. If I propose Cocoon as a platform for generic webapps, then I must be able to defend this view. I'm not sure that I can do it.
I've to give more thought on this though. thanks, Argyn > -----Original Message----- > From: Ryan Hoegg [mailto:[EMAIL PROTECTED] > Sent: Monday, February 24, 2003 6:12 PM > To: [EMAIL PROTECTED] > Subject: Re: presentation help needed: Cocoon apps > > > Hi Argyn, > > I'm not sure if you would consider this to fall under > "portals", but you > might also want to include its use as a platform for web > applications. > You could talk about XMLForms and Actions. > > -- > Ryan Hoegg > ISIS Networks > http://www.isisnetworks.net > > Argyn wrote: > > >Hello! > > > >I already wrote here, that I'm preparing a presentation on Cocoon. > > > >I'm almost done. I've one section left, which is about types of > >tasks/projects, where Cocoon can be used most effectively. > > > >I have this so far: > >Portals - obvious, I can say something about portal project too > >WebServices - both as a web service provider and consumer > >Publishing and document processing - obvious > >EAI and/or (Data mining and reporting)- Cocoon's aggregation > from data > >sources can be used for system integration - this is my favourite! > > > >Also, I'd love to get a project where I can use Cocoon vs > OLAP. I've a > >feeling that Cocoon's going to beat OLAP > > > >Ok, if you have any other suggestions, they'll be > appreciated and considered > > > >cheers, > >Argyn > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
