cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <>
Subject RE: XSP Woes
Date Wed, 01 Mar 2000 18:22:09 GMT
I switched to James Clark's XT, and I haven't had any problems with
XSL stylesheets not being processed or partially processed.  It seems
to be farther along than Xalan.  So... until Xalan achieves the stability
of Xerces and Cocoon, I will be using that for my more "mission
critical" stuff.  As for the rest of it, I can wait until the next release
before I update (I already updated the version problem with the samples).

-----Original Message-----
From:	Stefano Mazzocchi []
Sent:	Wednesday, March 01, 2000 10:27 AM
Subject:	Re: XSP Woes

Berin Loritsch wrote:
> In my (fresh) install of Cocoon-1.7, I noticed a couple of things
> about the XSP sample pages included.  Both were errors on my
> estimation, and I was curious if somebody else ran into these
> problems:
> 1) Cocoon always complained that the XSL stylesheet needs a
>     version number (this is really XSL issue, but it comes up).


> 2) The First XSP Page (pure content version) doesn't seem to
>     work properly--all the request information is not displayed
>     (my assumption is that the XSP logic page is not called).


> 3) The namespace version works correctly, BUT when I click
>     on "the servlet request library logicsheet" or "the utility library
>     logicsheet" links, I get a "
>     unknown protocol: resource" due to the following parameter:
>     url=resource://org/apache/cocoon/processor/xsp/library/java/request.xsl

fixed by removing it (it cannot work anymore due to other issues)
> 4) Lastly, when I use JMeter with multiple threads (I ran it with 10
>     and 20 threads) calling an XSP page, there was an intermittant
>     problem with the SAX parser not parsing all the elements.

Hmmmm, I'll investigate this further but Xalan has some multi-threading
problems... gone hunting...
> My setup is WinNT 4.0 SP 5, Tomcat 3.1, and Cocoon 1.7.  The
> first three are annoyances, but the last one is a serious issue.
> Before I can have my company deploy a site with hundreds of
> users hitting the site simultaneously (its a web app, not site), this
> issue needs to be cleared up.
> If Cocoon uses only one SAX parser for all requests, than it will
> undoubtedly run into issues.

Of course...

Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<>                             Friedrich Nietzsche
 Come to the first official Apache Software Foundation Conference!  
------------------------- http://ApacheCon.Com ---------------------

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message