Time to go back to JSP. Cocoon just isnt ready.

[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