[EMAIL PROTECTED] wrote:
For one thing, JSP (with Struts) is limited in scope to devices that support JSP pages (ie browsers). While JSP is slowly moving to other technologies/devices, Cocoon has already been structured to support virtually any type of device. That's what the XML buys you...create your view once in XML and send it to any type of device for interpretation by/for that device.
yep.
Mind also that you shouldn't compare JSP with XSLT in that respect.
JSP is mainly a templating language (meaning you shouldn't use the scripting logic features in there to conduct business logic processing)
While XSLT is an XML transformation language. (For that job it is designed and well equiped)
Inside Cocoon are a number of template languages that more nicely blend with the XML thinking (JXTemplate or the older XSP technology come to mind) and which should be the counterparts of your comparisson to JSP.
However, in Cocoon the 'view-template' is just one part of the equation, there is also often the multi-channel publishing issue. As Robert says, sometimes you want to yield from one template a multitude of different output formats (possibly for multiple devices) and maybe even want those aggregated/included in different ways.
If you know the Martin Fowler Enterprise Architecture patterns [1], I'ld say the Cocoon pipelines offer a very flexibile way to nicely mixing all of the TEMPLATE_VIEW, TRANSFORMER_VIEW and TWO_STEP_VIEW patterns, allowing you to use, combine and maximize all of their benefits for your set-up.
And last but not least, stepping away of only the 'view' issue: for more complex interaction sites you can benefit from the Cocoon Forms (comparable to JSP) and Cocoon FlowScript (quite unique IMHO).
Concluing: There is no simple unique one-size-fits-all Truth, but rather some negotiation towards the framework that best fits your needs.
From your message I get that JSP is enough for your current needs, so why bother? The good news is that Cocoon will not turn it's back on you. If your needs grow over time and the Cocoon feature mix starts showing its benefits, then we provide enough JSP minded components to ease the transition...
HTH -marc= [1] http://martinfowler.com/eaaCatalog/
HTH Bob
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, March 12, 2004 8:34 AM To: [EMAIL PROTECTED] Subject: Coccon vs. JSP
Hello!!
I am learning a lot about Cocoon, but I can't see yet the advantages of
Cocoon versus technologies like JSP. I think that working with XSL is much
more difficult than working with JSP, as XSL is limited in variables,etc.
What are the benefits of using Cocoon? (No doubt that you will change my
mind ;).
Alejandro
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Marc Portier http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center Read my weblog at http://blogs.cocoondev.org/mpo/ [EMAIL PROTECTED] [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
