It turns out that my employer wants to use Turbine for the next project.
Part of the issue is the lack of documentation and the very high learning
curve for Cocoon 2. Once I have put something together for Turbine, I will
have a better understanding of how that project approaches things. This
in actuality will be better for all of us.
The reason being that I want to be able to create more of a synergy between
the projects--and the only way of doing that is using the other projects.
I will have to get used to the way they accomplish the things that Cocoon
tries to accomplish. Who knows, I might find out that there are better ways
of accomplishing things in Cocoon, and be able to propose some well thought
out approaches. I have a feeling that by the time we are ready to release
Cocoon 2.2 (or Cocoon 3) we will have a more unified front for the Apache
Java web projects. None of them are perfect, but they are constantly
approaching that standard.
I wish I had the time needed to put together a guide for Cocoon like I did
for Avalon. Since we are a small comany, we have to put our efforts where
the money is--and Cocoon is almost too complex for new developers to jump
into it (for small teams). I will keep you guys posted and will remain
subscribed to the mailing lists. I am still a champion of Cocoon and Avalon,
and will remain so for the forseeable future.
S/MIME Cryptographic Signature
