Cocoon with Tomcat

[Michael Quattlebaum <mi...@mindspring.com>]

I have set up cocoon and tomcat, and they seem to be working fine.  Tomcat
serves JSP pages with no problems, and Cocoon seems to serve both XML and
XSP fine.  However, I would like to take a JSP page, make a method call that
returns XML, and then have Cocoon process it through XSLT.

When I launch the JSP page, it comes back to the browser nicely as an
XML-structured form, but is not processed using the XSL stylesheet.  If I
save the source file that is returned as an .xml file, and then bring it up
in the browser, it serves it correctly.  In otherwords, Cocoon is not
processing the JSP results.

Any ideas on how to get this working?

Michael Quattlebaum
michaeleq@mindspring.com

Re: Cocoon Vs. Cold Fusion

[Berin Loritsch <bl...@infoplanning.com>]

Ruud Prein wrote:
> 
> Could anyone tell me the advantages of Cocoon to a product like Cold
> Fusion. Or could someone tell me what Cocoon can do but Cold Fusion
> cannot do (or the other way around). Having a programming background, I
> would like only the 'presentable' end result to be taken into
> consideration.
> 
> I would be grateful is anyone could comment on that.
> 
> Thanks in advance.
> 
> Ruud Prein.

I think I can be qualified for this answer.  I spent the first 4-5 months
at my office writing a web application in ColdFusion.  The original state
of the project before I came on was a mess.  The application had a different
look and feel for each section of the site (depending on who the author
was).  It took a month and a half to get all the templates to look like each
other because the look of the page is inextricably tied to the code.

It took another month and a half to get the pages optimized so that Netscape
didn't have to spin it's wheels for 15 seconds once the page was downloaded.

After this period was over, I did a demonstration of Cocoon that put the
look on the site in a fraction of the time.  It was very easy to incorporate
logic separately.

The advantages of Cocoon are separation of concerns: the stylesheet, the XML,
and the Logic are able to be kept separate.  This results in more understandable
and readable code/templates.

In ColdFusion it is all connected in one huge mess.  I cringe everytime I look
at the ColdFusion code.  With Cocoon being a Java Servlet, has access to
everything that the Servlets have access to.  You would even be able to connect
to an Application Server to get EJBs and such.

The bottom line is for sites that have dynamic information, Cocoon is probably
better.  ColdFusion, while easy, encourages poor coding habits and does not
support good design.

Re: Cocoon Vs. Cold Fusion

[Uli Mayring <ul...@denic.de>]

On Mon, 17 Jul 2000 ruud@slowy.bagijnhof wrote:

> Could anyone tell me the advantages of Cocoon to a product like Cold
> Fusion. Or could someone tell me what Cocoon can do but Cold Fusion
> cannot do (or the other way around). Having a programming background, I
> would like only the 'presentable' end result to be taken into
> consideration.

cocoon is OpenSource and standards-based, whereas CF is proprietary. In
terms of what you can do with these products: with cocoon you can do
everything that you can do in Java. With CF you can do everything that you
can do in CF.

Ulrich

-- 
Ulrich Mayring
DENIC eG, Softwareentwicklung

Cocoon Vs. Cold Fusion

[Ruud Prein <Ru...@Prein.net>]

Could anyone tell me the advantages of Cocoon to a product like Cold
Fusion. Or could someone tell me what Cocoon can do but Cold Fusion
cannot do (or the other way around). Having a programming background, I
would like only the 'presentable' end result to be taken into
consideration.

I would be grateful is anyone could comment on that.

Thanks in advance.

Ruud Prein.
--