XSP - Identifier expected : xspParentNode = xspCurrentNode

This is the error message I keep receiving: 31: Identifier expected. xspParentNode = xspCurrentNode; ^ I am using Tomcat3.2.1 cocoon1.8.2 My code is: http://www.apache.org/1999/XSP/Core";> java.lang.* String fname = request.getParameter("fname");

[ANNOUNCE] XSLT-process 2.1 available

What's new? === This release adds few improvements to the previous release: - the ability to process the result of an XSLT transformation through the Apache FOP processor. - initial integration with the DocBook-XSL project; HTML and PDF generation and viewing from within Emacs of DocBoo

XSP: Type and Identifier errors

Hello, I am receiving this error: java.lang.Exception: XSP Java Compiler: Compilation failed for _newUser.java 72: Type expected. Class.forName("org.gjt.mm.mysql.Driver").newInstance(); ^ 240: Identifier expected. xspParentNode = xspCurrentNode; -^ The ligne 72:

RE: Dreaded: Sitemap handler's sitemap is not available

Srini, Thanks for your thoughts. May I ask some clarifying questions? Regarding Sitemap... is there instructions on how to compile Sitemap on C2 startup? I am not sure I know what do do here? This could be the watershed event. When you say restart the server... I assume you mean Tomcat or Co

RE: Dreaded: Sitemap handler's sitemap is not available

Hi Liam, I tried copying all the files from /home/cocoon/lib to the /home/tomcat/lib directory with no success. I had actually tried this before I sent the email and the log files ended up looking the same as it did without copying the jar files. I uninstalled everything and then reinstalled pe

Re: Dreaded: Sitemap handler's sitemap is not available

I found it necessary to include more jar files. Specifically, ALL the jar files :o) For example, I'm pretty sure the avalon jars get used, so that might be part of it. Also I think that when I built there was a difference in the files size between the cocoon.jar that came with installation and the

Re: Dreaded: Sitemap handler's sitemap is not available

Dear Ted and all the rest, This is exactly what happened to me when I tried to install Cocoon2 b2. In my case, I have already installed Cocoon2 b1 without a problem, and it happened when I tried to move to beta 2 maintaining exactly the same configuration (Windows2K, Tomcat 3.2.3, Sun JDK 1.3.1

Re: Dreaded: Sitemap handler's sitemap is not available

Hi., I hate to say "search the mail archive" but here is simple explanation... 1. Sitemap is one BIG java program to be compiled on c2 startup... 2. Any problem resulting from sitemap compilation could result in sitemap being NOT compiled and hence "component for hint: sitemap not found".. 3.

Dreaded: Sitemap handler's sitemap is not available

Folks, I am running the following: RedHat 7.0 Tomcat 3.2.3 Cocoon 2b1 JDK 1.3 I have installed, reinstall, read http://xml.apache.org/cocoon2/install.html, read the README, INSTALL, FAQ, searched the mailing list archives until I could not find any further refere

AW: formatting from the DB coming out as text

Use get-xml from the esql logicsheet in your xsp pages and the copy-of XSLT-Command in your XSLT-Stylesheet. See several postings on this issue in this mailing list. Note that the XML in the database has to be a well-formed xml document with root node etc. Stefan > -Ursprüngliche Nachricht--

formatting from the DB coming out as text

I have news articles stored in the database. When I use Cocoon to extract them, "" is converted to "

", and so the actual formatting of the news article is not shown. How do I fix this? Thanks... --- Liam Morley "light the deep, and bring silence to the world. light the world, and bring