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
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]
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
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
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
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
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
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
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
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
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,
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
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
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
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
+
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
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,
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
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
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
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
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.
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
24 matches
Mail list logo
