Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <4BCC17EE.9050404@oulu.fi>
Date: Mon, 19 Apr 2010 11:44:30 +0300
From: Andre Juffer <andre.juffer@oulu.fi>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: Lowering in amount of users' posts?
References: <4BCA0D74020000D400019241@pta-emo.csir.co.za>
 <p2u9baa770d1004180317qb4feb5eez997624fad2e4e12@mail.gmail.com>
 <p2uf4e3488b1004180412s33267638la4ee329725f0aa8e@mail.gmail.com>
 <115689.9886.qm@web111308.mail.gq1.yahoo.com>
 <7C655C04B6F59643A1EF66056C0E095E03C5D6B5@eusex01.sweden.ecsoft>
In-Reply-To: <7C655C04B6F59643A1EF66056C0E095E03C5D6B5@eusex01.sweden.ecsoft>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

I pretty much agree with what Robby just wrote. There are certain 
differences of course between Cocoon 2.2 and earlier versions, which may 
be somewhat difficult to grasp. Maven is a standard build tool and it is 
well supported by Netbeans and other similar tools. It is easy to 
construct an cocoon application with Netbeans. Also, the use of Spring 
is a logical choice. It would takes a few days to learn, but it is worth 
the effort. If you already know Cocoon 2.1, the switch to Cocoon 2.2 is 
not really hard (again, takes a few days). All in all, as Robby 
indicated, it may take you a week or so to convert to C2.2.

The only concern I have is the level of documentation in C2.2 and also 
C3. On the other hand, some of documentation that was already available 
under Cocoon 2.1 that is also applicable to C2.2 (like 
flowscript/jxtemplate) could (should) have been transferred to C2.2.

I wish the development of cocoon 2.2 or cocoon 3 would continue. With 
the recent emphasis on RESTful web services, I believe that cocoon 2.2 / 
3 could become a major player in that direction. All the tools one would 
require for a RESTful web application are essentially available. Many 
representations (Json, XML, txt, etc) of resources can easily be 
prepared with XSLT. In that respect, I would claim that Cocoon was ahead 
of its time, because the ability to generate various representations 
from the same source (usually XML) was always seen as one of Cocoon's 
strengths. Also, the introduction of blocks in C2.2 is quite compatible 
with the way of thinking of RESTful URIs.

So, in my opinion, Cocoon is a great tool and we should continue to use 
it. And we should start ask questions again. Questions means interest 
and interest stimulates further development.

Best,
Andr�

Robby Pelssers wrote:
>
> Maybe the learning curve got a bit steeper for Cocoon2.2 but I 
> disagree that this is inherent to Cocoon itself.  Cocoon2.2 still 
> allows you to do use the sitemap as before and building a complete 
> webapp with optional usage of
>
> -          Flowscript/jxtemplate
>
> -          Cocoon forms
>
> -          Xslt
>
> -          �
>
> without ever having to write a single line of Java.
>
>  
>
> It took me 1 week to completely make the switch from Cocoon2.1.11 to 
> Cocoon2.2. And building blocks and wiring them up  (dependencies) in 
> the servlet-context.xml is really simple.
>
>  
>
> The switch to Maven is a generic tendency seen in all open source 
> projects, so not only Cocoon�. Who will tell when we all switch to 
> Craddle (and have to learn yet another build tool and programming 
> language Groovy).
>
>  
>
> And the switch from Avalon to Spring was also a complete logical step� 
> it has become the de facto standard for doing dependency injection and 
> it comes bundled with a lot of usefull integration classes for most 
> frameworks (Castor, XStream, Quartz, �) and AOP.   And for the ones 
> who still think the only decent JVM language is Java� think twice.   
> http://en.wikipedia.org/wiki/List_of_JVM_languages
>
>  
>
> If you ask me this discussion is more about people resisting change in 
> Software development in general because they have to adapt (again) to 
> new technologies.
>
>  
>
> Cheers,
>
> Robby Pelssers
>
>  
>
> *From:* Andreas Kuehne [mailto:akuehne@yahoo.com]
> *Sent:* Sunday, April 18, 2010 3:40 PM
> *To:* users@cocoon.apache.org
> *Subject:* Re: Lowering in amount of users' posts?
>
>  
>
> Hi,
>
> for me it's also true :
> Didn't see any real need to got to 2.2. or beyond ! 2.1 does anything 
> for me, huge apps with heavy load as well as quick solutions.
>
> To the major problem of cocoon is : It's ready ! No burning needs for 
> new functionality, no major tasks on the todo list. Fiddeling with 
> another base framework ( spring instead of avalon ) or build tool ( 
> maven vs. ant ) doesn't make any user more happy.
>
> I can do what I need any van even impress competitors with speed and 
> performance. Maintainance mode or not, I'm happy with it !
>
> Greetings
>
> Andreas
>


-- 
Andre H. Juffer              | Phone: +358-8-553 1161
Biocenter Oulu and           | Fax: +358-8-553-1141
Department of Biochemistry   | Email: andre.juffer@oulu.fi
University of Oulu, Finland  | WWW: www.biochem.oulu.fi/Biocomputing/
StruBioCat                   | WWW: www.strubiocat.oulu.fi
NordProt                     | WWW: www.nordprot.org
Triacle Biocomputing         | WWW: www.triacle-bc.com


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org