2.0.3 ClassNotFoundException
jdk1.3.0_02, tomcat 3.2.1 Am upgrading 2.0.2 - 2.0.3, though, as I've removed all cocoon files from webapps and cleared out tomcat's workfiles, effectively it's a new install. build runs through ok, and installs war in webapps (tried both 'build install' and 'build installwar'). When I start tomcat, it unpacks the war correctly, and afaics the jars are all put correctly in WEB-INF/lib. However in cocoon's error.log I find java.lang.ClassNotFoundException: org.apache.cocoon.Cocoon and in access.log there is also java.lang.ClassNotFoundException: org.hsqldb.jdbcDriver so it seems to be unable to find the jars for some reason. So, when I try and access localhost/cocoon I get a nullpointerexception. er, no doubt this is something stupid. What am I missing? - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to get HTML (not XHTML) from the HTMLSerializer (C2.0.1)
excuse me if I'm missing the point but, if the objective is to get br instead of br/, wouldn't it be far easier to use the html output method in the xslt script directly, and not use the HTML serializer? On Friday 12 Apr 2002 7:59, Nicola Ken Barozzi wrote: From: Yuri Gadow [EMAIL PROTECTED] Try with br name=br/ If you mean an XSLT using that syntax (otherwise, I guess I'm missing something), I'm afraid that doesn't help. It's a hack to get Netscape 4 to use that tag. If I write: html body ciaobr/ ciao/body /html in Netscape 4.7 I get: ciaociao but if I write this: html body ciaobr name=br/ ciao/body /html I get: ciao ciao I can also write br whattheheck=myhackytag/ and it's the same, the trick is putting in an attribute. In this way Netscape 4 can show valid XHTML, which is IMHO better anyways than br. Just write a stylesheet that converts adds an attribute to br/s and copies all other stuff, and you're done. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to get HTML (not XHTML) from the HTMLSerializer (C2.0.1)
On Friday 12 Apr 2002 17:24, Yuri Gadow wrote: in every case I do live under the impression that the html serializer will create br for you instead of br/ did you check your sitemap? It does not. I just tested this, Yuri (I'm using 2.0.2 with xerces/xalan as provided). Put br/ in xsl file. With html serializer, it outputs br; with xhtml serializer, it outputs br / (that's with a space). This is surely exactly what you want, isn't it? - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: documentation for managers, was HP-SOAP Server announcement
On Friday 12 Apr 2002 12:43, Matthew Langham wrote: But you know, questions like: what business objectives does it help meet and how are really difficult to answer in a way that would suit all scenarios. I would certainly agree with that. Even trying to define what Cocoon is is not so simple. But then that's true of many useful things (such as computers, internet, electricity ...) Nevertheless, it has to be clear what the benefits of Cocoon are, i.e. why you would want to install it, and this has to be explained - together with the drawbacks - in a manner that non-specialists, especially decision-makers, can understand. That being said, I also think we need some form of Applied Cocoon - whether that be additional documentation such as best practices, tutorials. I consider 'applied' to be the key word there. Start from the objective (I want to publish my data in 5 languages on the web) and show how Cocoon can meet it and what it takes. To some extent, the existing samples do that, but the information is scattered around and it takes a lot of time to follow it all through - time which most of us simply don't have. I feel this will be something that is done on a per case basis. Tell me your problem and I will tell you how Cocoon (+ any additions) can solve it (assuming it can). meaning that Cocoon can only be implemented by specialist consultants working in an ad hoc manner? That doesn't sound like a very large install base to me. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: documentation for managers, was HP-SOAP Server announcement
On Wednesday 10 Apr 2002 12:58, Brent Eades wrote: I do agree with comments in an earlier thread about the need for more detailed docs for Cocoon. My colleagues and I are of similar skill levels: we're managers with IT and communications backgrounds, all of whom do a little coding as required, but we're primarily project leaders. We're not hard-core developers. And I know we do find aspects of Cocoon (and server-side Java in general) a little baffling still. A lot of unfamiliar concepts and procedures to master. I have the same problem, tho from a different standpoint. I do a lot of consultancy for small businesses and non-profits, most of whom have tiny IT budgets - many have no IT staff at all. In principle, Cocoon is of interest, but the key question is: is it worth the effort and the extra overhead of using Java? What I'm looking for (and don't find in the documentation) is answers to basic management questions like 'what advantages does Cocoon provide, i.e. what business objectives does it help meet and how?' 'how easy is it to implement?' 'what resources (time, skills level of staff) does it require to (a) get up and running (b) maintain?' plus standard operational questions like performance and security. I've been trying to evaluate Cocoon for several months now (off and on), but still don't really have the answers. For an organisation that is already supporting a servlet environment with XML etc, implementing Cocoon would probably be quite straightforward, but for those I'm dealing with who just want a good way to maintain a website? Ok, it may well use 'pipelined SAX processing' and an 'abstracted environment' - so what? I too would be happy to help out with documentation, but don't really see how, given that I don't really know that much about Cocoon. I'll write the questions; someone else can write the answers :-) - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Charting
On Friday 05 Apr 2002 18:58, Nicola Ken Barozzi wrote: From: Nicola Ken Barozzi [EMAIL PROTECTED] Ok, so I've managed to import the charting classes on sourceforge, under my krysalis.org project. had me confused for a moment. Seems we have 2 krysalises (krysales?). Do you know Interakt's Krysalis www.interakt.ro/products/Krysalis - basically a cut-down PHP implementation of Cocoon (also suffers from incomplete documentation)? - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Another database connection problem and cocoon hang!
silly question, but is your MySQL server actually running on port 9002 and not the usual 3306? Can you access it using the standard mysql client? Have you tried the mm.mysql test suite to access it via the Java routines? When it's working properly there, then try with Tomcat/Cocoon. Database connection problems are unlikely to have anything to do with Cocoon. On Saturday 06 Apr 2002 21:12, James Harris wrote: Hi I'm a bit of a newbie as far as cocoon is concerned but I am hoping someone can shed some light on my perplexing problem. I have been trying to get cocoon to connect to a database. I have cocoon serving static content and xsp pages which are transformed using stylesheets into html for display. I now want to drag some content for these xsp pages from a mysql database. I have followed some of the previous email discussions on this list and think I have the bases covered as far as configuration goes. Unfortunately, upon adding the following to my configuration, Tomcat seems to halt halfway through loading. This is cured by commenting out the org.gjt.mm.mysql.Driver line from web.xml. I don't know what the problem is when loading this driver. My cocoon.xconf looks like this (please don't judge me by the passwords): datasources jdbc name=mypool logger=core.datasources.mypool pool-controller min=5 max=10/ dburljdbc:mysql://localhost:9002/pms/dburl userjim/user passwordjim/password /jdbc /datasources My web.xml in WEBINF looks like this: init-param param-nameload-class/param-name param-value !--For mySQL:-- org.gjt.mm.mysql.Driver /param-value /init-param I have put the jar driver file containing the driver in my jdk\jre\lib\ext directory and even tried unjaring it and putting the org... directory tree in the classpath. Nothing seems to work. Following some previous threads on the subject and can answer YES to the following that were posted by Andrey Demchenko (but I do not really understand what the relevance of 3) is): 1) You must have jdbc driver file in classpath 2) Check your cocoon.xconf for datasources.../datasources for pool configuration 3) See access.log for message like this DEBUG (2002-03-26) 17:04.45:713 [access] (Unknown-URI) Unknown-thread/Cocoon Servlet: Trying to load class: org.gjt.mm.mysql.Driver One extra point to note is that I have cocoon serving pages from http://localhost:8080/mydir/ rather than from the cocoon directory. I achieved this by following the directions of Leigh Dodds tutorial on ibm.com/developerWorks and creating a directory structure as follows: Tomcat\WebApps\cocoon...(all the usual stuff in here) \mydir\mycontent \WEB-INF \cocoon.xconf If you have read the tutorial you will know what I have done but basically I created my on directory to hold my web app in the WebApps directory of Tomcat and just coppied the WEB-INF directory and cocoon.xconf from the cocoon directory to the one I created. This allowed cocoon to work fine until now. Could it be that by doing this I am having problems with tomcat trying to read in drivers twice from both web.xml files or something? I have tried many combinations of where to put the driver files and tried the org.gjt.mm.mysql.Driver in both web.xml files (in the cocoon dir and mydir) but still tomcat seems to hang half way through loading. It wont even serve its own homepage! Can anybody help - this is desperate. I am writing an app for my dissertation and if I cant connect to a database then there goes any chance of a decent degree!!! Many thanks Jim Harris - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Minimal Requirements
On Tuesday 02 Apr 2002 2:23 pm, Vadim Gritsenko wrote: From: Peter Robins [mailto:[EMAIL PROTECTED]] Just tried this with 2.0.2: my docs etc plus core cocoon. However, it tries to generate the cocoon documentation and the scratchpad as well, which I don't want in my production environment. Is there a way to produce the webapp without these (other than creating my own build.xml of course)? It just compiles and packages scratchpad.jar, it isn't going into WAR if no special option specified. it creates an avalon.excalibur.scratchpad jar - or is that something else? Or, you can rm -rf scratchpad/src/* No, scratchpad/src has to be present or it fails. However, I've since discovered that you can have an empty src/scratchpad/src and an empty src/documentation/images and it runs through happily. You can then delete the (empty) documentation in the war! Also, although the cocoon jar is quite a bit smaller than the default, it's still not entirely clean. For example, I see hsqldb/Server.class in there, even though I'm not using hsqldb; also some deli classes even though I'm not using deli. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Minimal Requirements
On Wednesday 03 Apr 2002 15:43, Vadim Gritsenko wrote: Also, although the cocoon jar is quite a bit smaller than the default, it's still not entirely clean. For example, I see hsqldb/Server.class in there, Server class is abstract Server, not the HSQLDB server. even though I'm not using hsqldb; also some deli classes even though I'm not using deli. Make sure to build clean after adding/removing any lib as described in the installation manual. yes, did that (yes, Vadim, I do read your postings :-) - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Minimal Requirements
Just tried this with 2.0.2: my docs etc plus core cocoon. However, it tries to generate the cocoon documentation and the scratchpad as well, which I don't want in my production environment. Is there a way to produce the webapp without these (other than creating my own build.xml of course)? On Sunday 24 Mar 2002 3:07 am, Vadim Gritsenko wrote: Here is the way (assuming you have source distribution): 1. build clean 2. remove all JAR files you do not need from the lib/optional (consult installing/jars.xml document on the disk or on the xml.apache.org site) 3. remove all pipelines from the sitemap.xmap, leave one map:pipeline with at least map:generate, map:transform (optional), map:serialize. You may want to have one pipeline with the map:read also for static resources. 4. remove all unneeded components from the sitemap.xmap 5. visit cocoon.xconf, check may be you do not need something there also (say, XSP language or certain XSP logicsheets) 6. build -Dinclude.webapp.libs=yes webapp Here it is, Cocoon webapp as you want it. Regards, Vadim - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why isn't Cocoon making into the commerical world?
I agree with you, but this is a common problem with open-source software. I have exactly the same problem with many of the programs in the Linux world - brilliant pieces of software produced by people with quite extraordinary dedication, but very badly presented/'marketed'. As a breed, programmers are much more interested in (and consequently better at) coding than they are in explaining. To be fair, Cocoon's documentation is much better than most, but I agree with you on the learning curve. The way Cocoon is packaged is a bit like someone wanting to learn to ride a bicycle, and being presented with instructions for that mixed in with instructions for driving a car, driving a tank, running an aircraft-carrier, and flying a 747, and then being left to work out which bits belong to which. This is not a good way of teaching people how to do things. The problem with the lack of tools is not really Cocoon-specific: there is a general lack of good ways of letting non-specialist end-users maintain XML/XSLT files. Few non-programmers use editors, and if they do the chances of them screwing things up are high! On Friday 29 Mar 2002 3:11 am, Rob Jellinghaus wrote: I think that Cocoon is designed and built mostly by programmers, and hasn't been marketed well (or indeed at all!). IMHO the main difficulty with Cocoon right now is how hard it is to learn. I am spending most of this week just coming to grips with the basics. It is *not* easy to dive right into the system and understand (say) exactly how the esql sample page gets converted into html (i.e. what exactly are all the steps of the pipeline, and where are they defined in the various sitemaps / logicsheets / stylesheets). Nor is it easy to know where to start when creating a new site, with a new CSS foundation and all new templates. Right now Cocoon is really best suited for programmers with lots of time to learn a new (albeit powerful) tool. In order to get wider adoption, Cocoon will need *even more* attention paid to making it easy for newbies to start working with it -- not only more tutorials along the lines of CTwiG, but also more (and more functional!) sample applications, and probably even more web-based management tools (since doing *all* Cocoon administration by editing XML files is not exactly easy -- try out Zope for an example of a different, simpler, approach). I do still like Cocoon, in theory, but the learning curve is daunting and it's still not clear I will be able to spend enough time on it to start getting good results. Cheers, Rob - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Database connection problem
I had a similar problem, Derek, which I eventually tracked down to authorisation problems. My DB was set up for user@localhost, and the driver was trying to connect with [EMAIL PROTECTED] When I added this authorisation to the MySQL tables, it worked w/o problem. Yours may be a different cause, but it looks like the driver can't connect to the DB for some reason. On Wednesday 27 Mar 2002 6:38 am, Derek Hohls wrote: 1) The jdbc driver file is loaded under: WEB-INF/classes/ 2) The xconf file contains: datasources jdbc name=my_connection pool-controller min=5 max=10/ auto-committrue/auto-commit dburljdbc:mysql://localhost:3306/mydbase/dburl userfoo/user passwordbar/password /jdbc /datasources 3) I am not sure what you mean by access.log - I only have cocoon.log and root.log in my WEB-INF/logs directory? The first enty in the cocoon.log has the line: FATAL_E (2002-03-26) 15:31.06:158 [cocoon ] (Unknown-URI) Unknown-thread/JdbcConnectionPool: Excalibur could not create any connections. Examine your settings to make sure they are correct. Make sure you can connect with the same settings on your machine. The root.log has no entries in it at all... Thanks for responding - any comments on the above?? Derek [EMAIL PROTECTED] 26/03/2002 05:11:18 1) You must have jdbc driver file in classpath 2) Check your cocoon.xconf for datasources.../datasources for pool configuration 3) See access.log for message like this DEBUG (2002-03-26) 17:04.45:713 [access] (Unknown-URI) Unknown-thread/Cocoon Servlet: Trying to load class: org.gjt.mm.mysql.Driver - Original Message - From: Derek Hohls [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, March 26, 2002 4:43 PM Subject: Database connection problem When trying to connect to a mySQL database, I get: Could not get the datasource java.sql.SQLException: There are no connections in the pool, check your settings. I already have the setting for the driver in the web.xml; init-param param-nameload-class/param-name param-valueorg.gjt.mm.mysql.Driver/param-value /init-param I can also connect to, and 'see' the database with another, front-end program. In fact, the connection AND database were working previously - does anyone know if a mod_rewrite for the site in the Apache server would affect this?? (seems strange, but thats the only major change that has happened on the server that I know about) I have also checked the connection without using the VirtualHost and get the same results... Any ideas as to what else to check? Thanks Derek - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Src vs bin download
As I'm not really interested in the actual sources, I would normally download the bin file. However, is it still the case that if I want a cutdown core installation I'm better off getting the src and running the build routine? With the distribution file getting ever bigger, on my slow connection, downloading 17MB is a lengthy procedure and I prefer not to have to do it twice! Do the tar.gz and zip files have the same content? Seems strange that the zip file is so much larger. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Request] Upgrade instructions for new releases
I was meaning as part of the documentation for the release. It will surely vary depending on the release: simple bugfix releases won't require much, extensive changes to sitemaps will. On Wednesday 20 Mar 2002 12:56 pm, Nicola Ken Barozzi wrote: From: Peter Robins [EMAIL PROTECTED] If a new release is imminent, can we please have instructions for those who are upgrading rather than installing from scratch. Upgrading is not simply a matter of copying over a war: the workfiles need to be cleared, there may be changes needed to sitemaps or configuration files. After the last upgrade, quite a few things on my installation stopped working; some were easy to fix, some still don't work, and the documentation wasn't very helpful. The basic rules are: 1. delete work dir 2. change jars 3. use the latest cocoon.xconf version and modify that 4. if you use Tomcat versions 4.0.(2|3) read workaround info for install in mailing list archives. 5. check that the components in the sitemap conform to the ones in the example sitemap - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Request] Upgrade instructions for new releases
If a new release is imminent, can we please have instructions for those who are upgrading rather than installing from scratch. Upgrading is not simply a matter of copying over a war: the workfiles need to be cleared, there may be changes needed to sitemaps or configuration files. After the last upgrade, quite a few things on my installation stopped working; some were easy to fix, some still don't work, and the documentation wasn't very helpful. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Let's improve handle-errors/ (was: Re: Contents of map:handle-errors?)
On Sunday 17 Mar 2002 1:52 pm, Nicola Ken Barozzi wrote: In my experience, by far the commonest error is page not found, and by far the commonest cause of that is that the user has mistyped the url (or clicked on an incorrect link). So all they need is a simple message saying 'page not found, please check what you entered' - a simple read of an html file is surely the simplest way of doing this. Sure, you can do it. Make a stylesheet that outputs only that page in the handle-errors pipeline and you're done. yes, this did occur to me - in effect, have a transformer that ignores the output of the generator. However, this loses some transparency in the sitemap, as it's not so obvious what's going on. For me, the big advantage of Cocoon is not the 'separation of concerns', which I've been doing for years with Perl/PHP templating systems, but the sitemap, which provides a clean, simple, standardised way of defining processes on the site. If your sitemap matches 404 errors with a read of a page_not_found.html, then it's clear what's happening; if you have to look into an xslt script to see what it does, then it's not so clear. This is the weakness of the Perl/PHP method: you have to look into the script/'logicsheet' (read: you have to have a programmer around), so it's harder to figure out what's going on. I agree, and I'm working on a FAQBuilder, that gives more helpful messages based on info from a FAQ. hmm, sounds interesting The Cocoon webapp is a *sample*, not a template. ah, but I bet most people use it as a template. Going off at a tangent, in your previous posting, you mentioned correcting the sitemap DTD. It would be good if this could be checked against the actual logic and then implemented properly. At the moment, it seems in some places to be incorrect, so can't be used for validating. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Security/encryption
That's a different issue, Joe. SSL encrypts the flow, and is not specific to Cocoon. I wouldn't expect Cocoon to handle this. I'm wanting to encrypt the passwords (or other sensitive data) in the actual XML files, as, for example, Apache does with its htpasswd files. IMO, all passwords should be stored in encrypted form - doesn't stop the crackers, but makes life more difficult for them. On Monday 18 Mar 2002 2:47 pm, Joseph Jupin wrote: I'm going to answer this in terms of an SSL connection from a client to your webserver (Apache or Tomcat, etc)... In the Tomcat documentation it states that when an SSL connection is made, the connection is encrypted from the client to the webserver as in any normal webserver situation. The server itself is responsible for taking the encrypted stream, un-encrypting them and then forwarding them on to the respective called for agent (in this case Cocoon)... So, Cocoon would only be as secure as the level of SSL encryption employed by your container webserver (128 bit, for example)... Please look at the Tomcat startup page and click on their Security-HOW-TO section... cool. peace. JOe... On Sat, 16 Mar 2002 19:30:49 + Peter Robins [EMAIL PROTECTED] wrote: On Friday 15 Mar 2002 11:07 pm, Vadim Gritsenko wrote: How do you handle plain text DB password in the weblogic's config.xml file? Or in the JRun server's local.properties file? Or Tomcat's server.xml? I don't. I don't use weblogic or jrun, nor do I have passwords in server.xml I guess that you can apply same technique to the Cocoon's cocoon.xconf. PS Cocoon uses Avalon's JDBC pools, so you may want to ask this on Avalon list. the question wasn't specific to DB, but a general question as to whether Cocoon handles encrypted data elements. However, looks like I have the answer - no :-) - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
More problems with handle-errors
Say I want to catch 404 errors with something like this: map:handle-errors type=404 map:transform src=xslt/error2html.xsl/ map:serialize/ /map:handle-errors If I only have 1 map:pipeline, this works fine: catches the error and executes the xsl. However, if I have 1 map:pipeline, it doesn't execute - I just get the standard miaow from Tomcat. I tried putting it in all map:pipelines, at the end of the last one, having it in its own map:pipeline (didn't like that), and nesting it in its own parent map:pipeline (didn't like that either). In the sample webapp supplied with cocoon, the handle-errors routine doesn't catch 404 errors either, but I see the syntax is different: instead of map:handle-errors having a type attribute, map:serialize has a status-code attribute - presumably this just effects the output stream, and has no effect on the actual error-handling? If no type attribute is specified, shouldn't it catch all errors? - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Security/encryption
On Friday 15 Mar 2002 11:07 pm, Vadim Gritsenko wrote: How do you handle plain text DB password in the weblogic's config.xml file? Or in the JRun server's local.properties file? Or Tomcat's server.xml? I don't. I don't use weblogic or jrun, nor do I have passwords in server.xml I guess that you can apply same technique to the Cocoon's cocoon.xconf. PS Cocoon uses Avalon's JDBC pools, so you may want to ask this on Avalon list. the question wasn't specific to DB, but a general question as to whether Cocoon handles encrypted data elements. However, looks like I have the answer - no :-) - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Let's improve handle-errors/ (was: Re: Contents of map:handle-errors?)
Nicola, istm you are making 2 false assumptions: 1. all errors are program errors 2. only the people who set up the site use it In any properly tested system, internal server errors and the like shouldn't (!) occur. Even if they do, there is nothing the user can do about it, so there's no point in telling them, apart perhaps from a simple message that there's a problem - please try again later or whatever. If a user gets a list of exceptions/java classes/whatever comes out of the generator, they won't understand a word of it anyway. The site administrator needs a report, so the problem can be fixed, but will get that from the logs. In my experience, by far the commonest error is page not found, and by far the commonest cause of that is that the user has mistyped the url (or clicked on an incorrect link). So all they need is a simple message saying 'page not found, please check what you entered' - a simple read of an html file is surely the simplest way of doing this. More user-friendly is to give them the message together with a standard menu of links to click on, which is why I was wanting an aggregate, but I'm not really bothered which map element is used to provide the page, whatever makes most sense. HTH p.s. if the sitemap compiler could similarly provide a more user-friendly message such as 'sitemap won't compile - pls check your xml is valid' instead of inscrutable messages about sitemap handlers, the amount of traffic in this list should decline significantly :-) p.p.s. don't have any arguments against your last point - TIA for any improvements On Friday 15 Mar 2002 5:21 pm, Nicola Ken Barozzi wrote: You brought out a thing that has been already discussed al lot on cocoon-dev, but AFAIK we didn't reach a conclusion that satisfies all. I hope you users can give me some hints on what you want. Has anyone arguments against this? in the following text are the points I would like to have feedback on. -- Design decisions on handle-error -- When I made the handle-error pipeline, I thought that it was made to notify the user of what went wrong. So I made up a simple DTD for it, and decided to keep it fixed. [Has anyone arguments against this?] To prevent misuse of this part of the pipeline that can come if you can define any Generator in it, I decided to keep the Generator fixed. The user can then manipulate the error XML to fit any style it needs. [Has anyone arguments against this?] There is also a need to access the error contents by actions and selectors. So I recently changed the works of this internally, and the sitemap model contains the error notification as an object, enabling it to be used by actions, selectors, etc. [Has anyone arguments against this?] Redirecting in this pipeline could be a problem, since it can redirect to a pipeline that has an error, which redirects to another one that has an error, and so on. [Has anyone arguments against this?] Using a Reader makes the recursive error problem still possible, since the Reader can read the pipeline it comes from, or any other pipeline that generates an error. [Has anyone arguments against this?] So, all these decisions mave the error handling what it is today. Comments, suggestions and constructive criticism is very welcome :-) So if I get enough feedback, I will modify handle-errors to make it more useful. [Has anyone arguments against this?];-) - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Contents of map:handle-errors?
In my 2.0 setup, I had a map:handle-errors with a simple map:read of an html file. This worked fine. However, with 2.0.1, this no longer compiles. I looked in the documentation (yes, really!): sitemap.html describes something called map:error-handler (I assume this is an, er, error) and says that you do not define a generator inside the error handler. Beside this issue you configure the error handler like a pipeline. Thus you can choose your transformer, and serializer, and all other features of pipeline processing If I look in the DTD on the other hand it tells me I can have generators, xformers and serializers (sic: what would I do with more than 1 serializer?). I tried adding read to the DTD but this had no effect - which didn't surprise me, as afaics the DTD isn't actually used by anything. Although read would, istm, be the simplest way of handling page not found errors, what I actually want to do is an aggregate, but the compiler doesn't like that either. Nor does it like a redirect or the cocoon:/ protocol. So, how can I get a handle on this error, and handle without error those errors that the handle-errors error-handler won't handle? ;-) - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problems with loggers
I recently upgraded from 2.0 to 2.0.1. Have 2 directories in tomcat/webapps, one for Cocoon as provided, one for my own application. In 2.0 the logging worked fine, with each writing to its own logfiles. With 2.0.1, this no longer works: each on its own (only 1 tomcat/webapps) works fine, but when I try and run both at once, the 2nd says 'error: could not set up cocoon logger' and writes everything to the console. I found a previous thread re this msg, but it referred to a different situation. Also, I can't get the logger to work in command-line mode. Regardless of what I put in the -k or -l params, it writes msgs to console. I think I'm missing something somewhere. I've looked at the logkit webpage, but can't see anything relevant. What do I have to change where to get the logger to write to its logfiles properly? - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: what is the easiest way to delopy cocoon application?
On Saturday 09 Mar 2002 8:28 am, John Austin wrote: Take a look at http://sourceforge.net/projects/Chello should read chello - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Relationship between pipelines and match nodes
I'm getting rather confused on what a pipeline actually consists of, and can't find any docu on this. In the sample sitemap, some match nodes are in their own pipeline, other pipelines contain many different matches. One pipeline contains its own error-handling definition, which implies that you can have different pipelines with differing error-handling routines (altho in this case it seems to be identical, so quite what purpose . . .). If so, what happens for those pipelines that don't have an error-handling definition? I eventually found a definition of the 'cocoon:/' syntax buried in the changes log, which says that it accesses another pipeline, yet in the documentation sitemap, the example doesn't go to another pipeline but to another match in the same pipeline. In any case, afaics, there is no identifier for pipelines. If these matches were all in their own separate pipelines, would the behaviour be different, and if so how? - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
