On 11 Apr 2002 at 10:46, Peter Robins wrote:
> In principle, Cocoon is of
> interest, but the key question is: is it worth the effort and the
> extra overhead of using Java?
A very relevant point. I suppose this is an issue facing all of the
Jakarta projects, the fact that besides selling open-source solutions
(a challenge itself in many organizations), you're also requiring the
introduction of a whole new platform. This is problematic for some of
my colleagues on this project; they would have to go through lengthy
approval processes in their respective organizations before they
could consider using Java/Cocoon in production. This is something
that Jakarta overall could probably spend a little more time
educating users about.
> What I'm looking for (and don't find in
> the documentation) is answers to basic management questions like 'what
> advantages does Cocoon provide, i.e. what business objectives does it
> help meet and how?' 'how easy is it to implement?' 'what resources
> (time, skills level of staff) does it require to (a) get up and
> running (b) maintain?' plus standard operational questions like
> performance and security.
Agreed, though certainly no one can be "faulted" for this. I was a
documentation manager at one time in my, er, varied career, and I
know that it's not possible to write comprehensive docs until the
product is mature and stable.
I do get the feeling that Cocoon is pretty near "ready for primetime"
by now, however. Time to "make the business case", as you say.
-----------------------------
Brent Eades, Almonte, Ontario
http://www.almonte.com
http://www.bankofcanada.ca
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
