Dear Community, caro Luca, 

Thanks for your short topic list. I agree with you, less is more ... and,
let us found the very important things to speak at the GT2007.

>From my point of view, Cocoon 2.2 and how to get there from 2.1.x would be a
very important input at the current state of the Cocoon development.

In the last 4 years, we have developed many applications based on Cocoon 2.1
(including SOA). And we are very happy on what this great XML framework did
and does for us. A part the presentation layer! Which we have substituted
with an own, cocoon independent, XSLT transformation step (that works also
nice with CForms).

But with 2.2 everything seams to be different. So, at the current state,
questions as "what is Cocoon 2.2?" and "how we migrate 2.1.x applications?"
are very important for us. If the GT2007 could also focus on this aspect we
would very appreciate it.

What do you think about it?

Raffaele  

> -----Ursprüngliche Nachricht-----
> Von: Luca Morandini [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 10. August 2007 13:57
> An: [EMAIL PROTECTED]
> Cc: [email protected]
> Betreff: Re: [GT2007] Request for papers
> 
> Andrew Savory wrote:
> >
> > Hmm, the list of ideas somehow got eaten by the mail daemons, so here's
> > the suggestions from last year. Anyone care to add anything?
> 
> Since the scenario has changed a bit since 2006, I'd rather like to hear
> something on these topics:
> 
> 1) 2.2: what's in it for me ?
> 2) Shall we move Cocoon from service-oriented to resource-oriented to
> better support RIA/Ajax/Web 2.0/<insert your own bizzwords> ?
> 3) CForms vs Apache-Wicket
> 4) Some success stories on TDD (and the best tools for the job).
> 
> Regards,
> 
> --------------------
>     Luca Morandini
> www.lucamorandini.it
> --------------------
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to