Alex,
I just copied my cocoon directory in a Tomcat 5 installation.
The problem persists. So, it's not Jetty related either
BUT ...
looking into the stacktrace a bit better, i notice this
Original Exception: org.apache.avalon.framework.CascadingRuntimeException: Error getting ascii data
Pfff, this is getting so frustrating.
I now recompiled my Postgresql, to make sure my initdb had the right encoding (latin1)
One simple XSP page, my output still looks like this
xml>
-
table>
-
tr>
td>Yves/td>
/tr>
-
tr>
td>éèà ç/td>
/tr>
/table>
/xml>
Can anyone please tell me whether
Ok, now I installed SQL4J on OSX. The same problem occurs there.
So it's not a Cocoon specific error.
How can I test if it's my JVM or my DB that is wrong ?
For the DB part: I tried to connect through ms Access and everything is okay.
For the JVM part: I have it on both Linux as OSX.
On 30 Mar
I am not aware of having done anything special to install Tomcat under
Mac OS X.
As far as I recall, I downloaded jakarta-tomcat-5.0.16.tar.gz from
Apache,
expanded it and started Tomcat with the bin/startup.sh which it
contains.
I built a WAR file from Cocoon with ant, copied it into the
But why do you need them ??
You can startup Cocoon 2.1 with Jetty (cocoon.sh servlet)
There's no need for Tomcat
On 28 Mar 2004, at 00:46, Stephen Winnall wrote:
On 27 Mar 2004, at 12:57, Yves Vindevogel wrote:
Why do you use Tomcat 5 and Cocoon 2.1 together ?
Cocoon 2.1.x runs with Jetty
On 28 Mar 2004, at 12:39, Yves Vindevogel wrote:
But why do you need them ??
You can startup Cocoon 2.1 with Jetty (cocoon.sh servlet)
There's no need for Tomcat
Ah...! No good reason really: I first used Tomcat when it was version
1.x and haven't had any reason to change. And since I am
I see could you please tell me how to setup Tomcat 5 so that it works with Cocoon 2.1. Or a document on line ?
This way, I could set up that solution and test if my problem is Jetty related. Because ... all my previous installations were on Tomcat.
Might be Jetty related ...
If Alexander
I downloaded Cocoon 2.0.4 (latest from 2.0 series) with VM 1.4
I dropped the cocoon.war in the webapps. Tomcat unpacks it.
I try to open the :8080/cocoon folder and I get this error
Failed to generate program code (this may happen if you use Xalan in
incremental processing mode). Please check
Yves Vindevogel wrote:
I see could you please tell me how to setup Tomcat 5 so that it
works with Cocoon 2.1. Or a document on line ?
This way, I could set up that solution and test if my problem is Jetty
related. Because ... all my previous installations were on Tomcat.
Might be Jetty
I run Tomcat 5 under Mac OS X 10.3.3 (and 10.3.2 before that) with no
problems.
What I have noticed is that it takes Cocoon a long time to start up
when Tomcat
is (re)started, which might explain your error message. I am using
Cocoon 2.1.4.
Steve
On 26 Mar 2004, at 20:51, Yves Vindevogel
Why do you use Tomcat 5 and Cocoon 2.1 together ?
Cocoon 2.1.x runs with Jetty here, on both machines.
I think the slow startup is due to the way Tomcat works, I guess.
Anyway, the latest versions of both are not functioning, but maybe I should let it do its thing for 2 minutes.
Are you sure
On 27 Mar 2004, at 12:57, Yves Vindevogel wrote:
Why do you use Tomcat 5 and Cocoon 2.1 together ?
Cocoon 2.1.x runs with Jetty here, on both machines.
I use them because they are the most recent versions, and I have no
reason
not to use them (i.e. they work).
Are you sure you combine both ?
I
Ok, I got my database going again on a different machine. I now use
Panther with the JVM that comes with it.
I use the driver compiled by postgresql, and have already tested the
one from their site. No solution.
When I use a basic XSP, with strange chars, it works.
So, it's only when I use
Yves Vindevogel wrote:
btw.: what do you mean with
mydatabase?charSet=iso-8859-1 dburl.
In your configuration of the datasources:
I use this to force Postgresql to send my everything in ISO-8859-1.
This works under Tomcat / Cocoon 2.0.x on Mac OSX 10.2 (no panther yet on
that machine)
jdbc
Le Mardi, 9 mars 2004, à 10:31 Europe/Zurich, Alexander Schatten a
écrit :
...I think I have really set everything that is mentioned in the
documentation, the wiki or the mailinglist:
-- LANG system variable
-- JAVA_OPTIONS on startup
-- this encoding in the driver
still the öäüÄÖÜ are not
I really believe now, this is a VM bug, but I am curious, that there
seem to be no other OS X user, that have upgraded the Java VM and did
not recognize this problem. (again: the application works fine and
without problems on Linux).
YV: I have the opposite. Running an old VM on my Mac (Jaguar
Yves Vindevogel wrote:
Yes, could be I use 1.4.2_03
What I also noticed ...
I use swaret to keep my system up-to-date. Swaret wanted me to install
XFree86 4.xx to run J2Sdk.
I think this is no longer needed (since 1.4), so I did not install it.
Could there be a problem there ?
really, I
btw.: what do you mean with
mydatabase?charSet=iso-8859-1 dburl.
In your configuration of the datasources:
I use this to force Postgresql to send my everything in ISO-8859-1.
This works under Tomcat / Cocoon 2.0.x on Mac OSX 10.2 (no panther yet on
that machine)
jdbc name=mypool
server, with the same datasource settings.
-Original Message-
From: Alexander Schatten [mailto:[EMAIL PROTECTED]
Sent: zondag 7 maart 2004 2:29
To: [EMAIL PROTECTED]
Subject: Re: [OS-X] Serious Encoding Problems (VM Bug?)
Yves Vindevogel wrote:
My problem (see: Bug in ServerPages Generator
Yves Vindevogel wrote:
jdbc name=mypool
dburljdbc:postgresql://myserver/mydatabase?charSet=iso-8859-1/dburl
/jdbc
hm, thank you; did not know this one; looks like a specific postgresql
feature, no? will this work on mysql too?
thanks
alex
I have no idea at all
but, I do think this is jdbc related and not postgres
-Original Message-
From: Alexander Schatten [mailto:[EMAIL PROTECTED]
Sent: zondag 7 maart 2004 17:03
To: [EMAIL PROTECTED]
Subject: Re: [OS-X] Serious Encoding Problems (VM Bug?)
Yves Vindevogel wrote
I had a similar problem storing German text in a Postgresql database
under
Mac OS X. I discovered that
1) Java stored data in the database in UTF-8;
2) Java does not necessarily read Strings in the format you would
expect.
I populated the database from a Microsoft Excel source using a Java
: [OS-X] Serious Encoding Problems (VM Bug?)
I had a similar problem storing German text in a Postgresql database
under
Mac OS X. I discovered that
1) Java stored data in the database in UTF-8;
2) Java does not necessarily read Strings in the format you would
expect.
I populated the database from
Yves Vindevogel wrote:
My problem (see: Bug in ServerPages Generator ??) could be related to this.
If I declare some string in Java within XSP, I have to use unicode for (in
my case) french characters. I now experience the same problems with data
coming from my database.
I think it could also
I develop certain Cocoon webapps on a Powerbook with recent cocoon
version; up to now with same config like on Redhat Linux and no problems
also iso-8859-1 (german) encoding worked fine: environment variable LANG
is set to de...
yesterday I worked on an application on the powerbook and
Le Vendredi, 5 mars 2004, à 16:22 Europe/Zurich, Alexander Schatten a
écrit :
...Has anyone an idea, how I could fix this encoding problem on OS X ?
Most probably, you need to make sure the JVM is started with the
correct encoding definition, like -Dfile.encoding=iso-8859-1
-Bertrand
Bertrand Delacretaz wrote:
Le Vendredi, 5 mars 2004, à 16:22 Europe/Zurich, Alexander Schatten a
écrit :
...Has anyone an idea, how I could fix this encoding problem on OS X ?
Most probably, you need to make sure the JVM is started with the
correct encoding definition, like
Alexander Schatten wrote:
JAVA_OPTIONS='-Dfile.encoding=iso-8859-1'
I read the Sun documentation now, and extended this to:
-Dfile.encoding=iso-8859-1 -Duser.language=de -Duser.country=DE
-Duser.variant=MAC
additionally,
-- the LANG=de_DE.iso-8859-1
-- the two encoding init params in web.xml
are you sure these java options are actually used when your servlet
container starts up? Do an echo $JAVA_OPTIONS just before the statement
you think gets exec'ed to start the container.
Alexander Schatten wrote:
Alexander Schatten wrote:
JAVA_OPTIONS='-Dfile.encoding=iso-8859-1'
I read the
I use Jetty.
java -Xmx256M -Xms128M -Xss128K -Dfile.encoding=UTF-8 -jar start.jar
etc/jetty.xml
Then it works fine.
teru
- Original Message -
From: Jorg Heymans [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, March 06, 2004 2:34 AM
Subject: Re: [OS-X] Serious Encoding Problems (VM
30 matches
Mail list logo
