On 19/apr/10, at 11:20, Robby Pelssers wrote:
> Ok.
>
> I have to agree on the documentation issue. This certainly hasn't
> approved and for usage of sitemap components I still tend to use the
> Cocoon2.1.x docs.
>
> I do believe as well that Cocoon forms in combination with
> flowscript was state of the art back then but other frameworks are
> doing an equally good or even better job nowadays.
>
> Cocoon is still my preferred tool to do xml transformations but if
> you want to build highly dynamic interactive webapps you might as
> well take a look around for other available options. But this is
> where Cocoon3.0 comes into play...
>
> Instead of building your complete webapp with the Cocoon framework
> you can now choose your preferred framework (GWT, Wicket, -> http://java-source.net/open-source/web-frameworks
> ) and outsource the xml stuff to Cocoon3 by just using the Java
> API. Also check out Reinhard's effort for howto http://cocoon.apache.org/3.0/reference/html-single/index.html#wicket-integration
>
> And I expect I'll make the switch to Cocoon3 over the next year
> because of this reason.
I totally agree with this approach: I personally see much of Cocoon's
future in Cocoon 3.
I am also considering to use it to build a REST interface for one of
our projects in Italy: I'll keep the list updated about how this is
going.
> On the other hand the first implementations of XPROC are available
> which resembles a lot what cocoon has to offer...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
|