RE: Modifying an xslt stylesheet before utilisation.

OK, some sloppy copying as well! Originally, this would look like: > > > > > > > So besides the request-parameters a paramater named path is also passed to the xsl, which can be helpfull. For instance, you're building a navigation, then the xml and xsl would be the same for

RE: Modifying an xslt stylesheet before utilisation.

:parameters. Almost, because you then have to define those > parameters in your xsl (of course) > > With kind regards / Met vriendelijke groeten, > > Rogier Peters > - > Content Management Department > Hippo Webworks

RE: Modifying an xslt stylesheet before utilisation.

/ Met vriendelijke groeten, Rogier Peters - Content Management Department Hippo Webworks Rogier(at)hippo(dot)nl / www.hippo.nl > -Original Message- > From: GB [mailto:[EMAIL PROTECTED]] > Sent: Thursday, July 18, 2002 2:26 P

RE: Using Xalan from the command line?

If you look here: http://xml.apache.org/xalan-j/commandline.html there's a good explanation of the command line utility along with all the flags you can set. I use it from xmlspy as an alternate to the msxml parser. Regards, Rogier P

RE: Barf on JSPGenerator on Hello.jsp (HELP!)

Hi guys, I'm sorry, but I'm also getting this error on a clean install of cocoon 2.0.2 on tomcat 4.0.1 The error is slightly different for jdk1.4 and 1.3.1 (see stacktraces below). By the way, I don't want to step on any toes here, but I think it's strange that when someone asks a question abou

RE: Memory leaks(?)

> > would this be a case for cactus? http://jakarta.apache.org/cactus :) > What is this? I use OptimizeIt. Downloading it now > > Vadim > > > > Rogier > > > - > Please check that your question has not already been answer

RE: Memory leaks(?)

Hi vadim > PS Consider using memory debugging tools would this be a case for cactus? Rogier - Please check that your question has not already been answered in the FAQ before posting. T

RE: Memory leaks(?)

Hi all, thanks for the quick reply.. > > > From: Rogier Peters [mailto:[EMAIL PROTECTED]] > > > > Hi, > > Hi, > > > We've been running cocoon for some time now, and we really like it, > but we > > keep having problems with memory usage. >

Memory leaks(?)

nd with the jvm -Xmx option, and with cocoon.xconf heapsize and cached objects, but that didn't help. I was wondering whether anyone had the same problems with cocoon, and I am of course very interested in solutions, tweaks, or configuration options that I may have overlooked.