cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Viktors Rotanovs <>
Subject Re: JSP vs. Cocoon for Website
Date Wed, 27 Sep 2000 17:54:36 GMT
Hi Jim,

you can use Enhydra or Turbine for interaction and
Cocoon for output. Cocoon is THE winner when you
have to deal with presentation, but is not very good
for complex interaction.

On Wed, 27 Sep 2000, you wrote:
> Dear Cocoon Users,
> I'm having a difficult time in deciding whether to use JSP or Cocoon for
> developing a Web Site which will sell items, have a fair amount of database
> activity, and security issues.  The site will also be sold to others and
> personalized, within reason.  I see that Cocoon with its XML/XSL technology
> is a clear winner for publishing.  But I'm not sure about developing this
> particular Website.
> Here is how I see it and I would appreciate any comments and definitely
> anything I missed with Cocoon as I'm new to it.
> Cocoon offers a lot of XML/XSL technology.  I know XML is THE buzz word
> lately, but I don't want to use Cocoon just for this.
> JSP is part of the J2EE standard, Cocoon has specific extensions like XSP,
> SQL Processor, etc., technology that would seem to lock me into Cocoon.  If
> I get mad at my J2EE vendor I can dump them for one of another dozen, with
> very little change.
> The site will have minimum content, but will have a lot of user
> interaction, collecting information for quotes, etc.
> Since my site will be customized for different customers with most of the
> data in the database already,  I don't see that I could take advantage of
> XML files.  I believe I would need to create, in Cocoon terms, a producer.
> Based on this I need to write a Java producer and thus Cocoon doesn't help
> me in this respect, as I need to create the XML on the fly anyway.  I could
> use the SQL Processor with Cocoon, but the client I am building the site
> for has a lot of stored procedures to calculate complex values.  It doesn't
> appear that Cocoon supports Stored Procedures, as they are database
> specific.  It seems I would be back to writing a producer.
> Both the JSP taglib and the XSL style sheet have similar logic statements,
> or processing instructions, allowing (for mostly) the separation of
> content, formatting and logic.  The logic area seems to be one area though
> that Cocoon offers a definite advantage.  I would have to write more Java
> code using JSP, whereas I could take advantage of built-in capabilities of
> If I use JSP I believe I would be able to take better advantage of the J2EE
> application server's fail-over capability, which the client already owns.
> It appears I can provide better security with JSP by using ACL's within the
> application server.
> It is possible the site will be used later to interface with WML and WAP.
> Again, it seems as though Cocoon would take less time because of built-in
> XSLT capabilities.
> The final decision seems to come down to content, formatting, logic and
> security.  As far as providing content I see JSP and Cocoon as even, since
> I need to write an XML producer in either case.  For formatting, again, I
> see them as about even as I need to put in the HTML in either JSP or XSL. 
> The advantage on logic would go to Cocoon since I could take advantage of
> XSLT, thus writing less code.  The advantage on security would seem to go
> to JSP.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Best Wishes,
Viktors Rotanovs
I create websites that attract more clients.
Riga Latvia +371, Phone 7377-142, GSM 9173-000, FAX 7377-472

View raw message