i agree partially on your opinion.
* yes, cocoon is complex to use, we are talking about this
since long time now...
* yes, cocoons documentation is complex and not complete.
* yes, it takes time to get productive on cocoon, maybe too
much time
* yes, debugging with cocoon is poor.
but...
in my eyes cocoon is something like a sandbbox for front end
technologies. People try out new things here and come with
new concepts there. It has more of an experimental playground
than a mature "professionl tool" (whatever that may implicate)
just to be clear: i like this very much, this keeps me living...
Despite that, i think you can use cocoon also in professional
environment if you do it carefully. Maybe you can't take the
full functionality and turn it into production under all
circumstances yet. But you can use it and benefit from it
right now. (i can and shurely others do)
Where the cocoon development has to take care is to
keep (or better get back to ?) a modular structure, so
it's entropy keeps low (there was an email about thermal
death some time ago).
Maybe we are far away from maturity, but we won't get closer,
if everyone interested in "professional" usage just skips it,
because it's "not professionally usable" right now.
Instead of coming back next year you may help getting there
by taking a little bit of care... You might benefit at the
end (no promise, but a chance)
I wonder, if there is a company out in the world, who
is already dealing with cooling down cocoon and packing
it as "professional distribution" ?
Wouldn't it be nice to get something like a "coconuts"
distrib with documentation all put together for instant
usage (today for experiment, tomorrow for production) ? ...
regards, Hussayn
Andreas Bednarz wrote:
Hi Robert,
I completely agree with your opinion and share your sorrows about the
current state. I personally use Resins XTP mechanism, which works fine
and fast and is well documented etc. Maybe some days we will change to
cocoon, but now ...
Andreas Bednarz
Am Don, 2003-01-30 um 12.21 schrieb Robert Simmons:
I have reluctantly come to the conclusion that cocoon is not ready for
professional development. Unlike tomcat, or Ant, this product has
serious things blocking its use in production systems. I personally am
completely and utterly stopped by the classpath bug indicated here:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16580. Just another
symptom of a product that needs more work to be used in professional
products. That coupled with the lack of documentation makes the
package difficult at best. I will possibly be back in a year or so
when this technology has gone somewhere. This is assuming it is still
alive by then. I have seen a plethora of new people come on this list
and then just vanish. That doesn't bode well for its reputation. I
don't want to take this step and throw away two weeks of work but the
fact is that I also don't have time to wait for such massive bugs to
be fixed and to spend another two weeks swimming through poor
debugging tools. Its a massive bummer to me but in order to be true to
myself I cant see alternatives. The fact is that however flawed JSPs
are, I can crack together JSP pagers 40 times faster than cocoon
pages. When it comes to deadlines, major bugs like this just stop a
product cold. Anyway, Ill stop rambling now.
Comments are invited.
-- Robert
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
