Looks like I confused the function of the EncodeURLTransformer with my need for
urlencoding of url parameter values :(
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
regardless of the chosen output
encoding (didn't catch it but I am assuming that the output-encoding is set
to UTF-8 anyways, and matches the form-encoding setting)
- so we get an html page out telling the browser it is utf-8 encoded
- so the browser will apply utf-8 encoding to form-values (and names
On Fri, 29 Oct 2004, Kees van Dieren wrote:
In mozilla Firefox, when you open the right-click menu and choose View
page Info what is the value for Encoding there?
The same than used in serializer configuration. No problem here.
The serializer still seems to use ISO-8859 (e.g. not UTF-8
Good morning Cocooners
I've run into trouble with my ESQL page. In detail:
I'm running an Oracle database pool and a few tables in there with CLOBs
which contain UTF-8 strings.
The following code extracts the data quite nicely:
oracle.sql.CLOB body = (oracle.sql.CLOB)esql:get-object
in Section B.2.1 of the HTML 4.0 Recommendation [2]. The
latter recommends that non-ASCII characters be represented in UTF-8
prior to applying the %HH escaping described by the URI RTF,
regardless of the output encoding.
nifty, didn't know... so whatever output encoding you set the uri's will
be utf-8
the method
recommended in Section B.2.1 of the HTML 4.0 Recommendation [2]. The
latter recommends that non-ASCII characters be represented in UTF-8
prior to applying the %HH escaping described by the URI RTF,
regardless of the output encoding.
nifty, didn't know... so whatever output encoding you
In mozilla Firefox, when you open the right-click menu and choose View
page Info what is the value for Encoding there?
The serializer still seems to use ISO-8859 (e.g. not UTF-8)(according to
the link problem)?
The serializer add's the encoding type to the resulting html page, just
behind
...adding to my latest post
The URL-encoding is done wrong when serializing to HTML. According to
specs äö should become %E4%F6 when encoded, not %C3%A4%C3%B6. This
seems to be the problem. So far I've noticed this problem with the
HREF-attribute only.
For a test I made a styslesheet
just scanning through this issue fast it seems to me like more evidence
of things expressed here:
http://marc.theaimsgroup.com/?t=10923117717r=1w=2
rehashing what I read from Tuomo's setup:
- cocoon-servlet init params are set to have container-encoding
unchanged (thus iso_8859_1) like we
Ok, now I'm really confused.
In Bruno's excellent paper about Cocoon encoding, there's a section that
says:
For Java-insiders: what Cocoon actually does internally is apply the
following trick to get a parameter correctly decoded: suppose value is a
string containing a request parameter
Tuomo L wrote:
Ok, now I'm really confused.
In Bruno's excellent paper about Cocoon encoding, there's a section that
says:
For Java-insiders: what Cocoon actually does internally is apply the
following trick to get a parameter correctly decoded: suppose value is
a string containing a request
Hi,
We're having some serious encoding problems. This happens only with the
@href attributes in html, when using characters like å, ä and ö (in
Finnish alphabet). Form encoding works just fine. I've gone through
all the threads concerning encoding (other people having encoding problems
too
On 28.10.2004 21:35, Tuomo L wrote:
We're having some serious encoding problems. This happens only with the
@href attributes in html, when using characters like å, ä and ö (in
Finnish alphabet). Form encoding works just fine. I've gone through all
the threads concerning encoding (other people
(DefaultXMLizer.java:16
2)
at
org.apache.excalibur.xml.xslt.XSLTProcessorImpl.sourceToSAX(XSLTProcesso
rImpl.java:401)
at
org.apache.excalibur.xml.xslt.XSLTProcessorImpl.transform(XSLTProcessorI
mpl.java:433)
... 42 more
How we change the configuration encoding to ISO-8859-1 in the xscript
transform
Henry Orlando Canastero dijo:
How we change the configuration encoding to ISO-8859-1 in the xscript
transform, for it can support the ñ and others Spanish characters ?
Hi Henry:
UTF-8 is able to support all spanish characters. I guess the problem is
more related to how are you encoding
some idea ???
Thanx.
-Mensaje original-
De: Antonio Gallardo [mailto:[EMAIL PROTECTED]
Enviado el: Viernes, 24 de Septiembre de 2004 04:12 p.m.
Para: [EMAIL PROTECTED]
Asunto: Re: Problem using xscript, encoding.
Henry Orlando Canastero dijo:
How we change the configuration encoding
Christian Hoofe wrote:
[...]
Put this into your sitemap.xmap to produce output IE understands:
map:serializer ...
omit-xml-declarationyes/omit-xml-declaration
/map:serializer
That's exactly what I already suggested in the second posting of this
thread. (Did you read it?).
But only
You should set the container-encoding to ISO-8859-1 and leave the
form-encoding as UTF-8. If I remember correctly, the container-encoding
is a thing introduced with servlet api 2.3 while cocoon was coping with
2.2 . The latter did pass everything in ISO and cocoon expects it to be
ISO
encoding iso-8859-1.
probably somewhere in the serializer
I made sure I had xml:output encoding=UTF-8 everywhere, but the
to no avail (and I assume you wanted to type xsl:output ... )
this directive is used by xalan if the 'xalan engine' is operating in a
mode where it needs to transform
Hi,
I'm using Cocoon 2.1.5.1 w/ Jetty 4.2.15. xalan was throwing a
SAXException trying to write a character (U2026, hellip) that's not
reppresentable in the specified output encoding iso-8859-1.
I made sure I had xml:output encoding=UTF-8 everywhere, but the
problem persisted. Finally I
Bjrn Voigt wrote:
Hello cocooners,
I use the velocity-generator to load an utf-8 encoded XML-File and fill
in a UTF-8 encoded sitemap-parameter. OK the is parameter filled in
correctly
but the file seems to be decoded in ISO-8859.
Is it possible or how is it possible to configure the generator
Hello cocooners,
I use the velocity-generator to load an utf-8 encoded XML-File and fill
in a UTF-8 encoded sitemap-parameter. OK the is parameter filled in
correctly
but the file seems to be decoded in ISO-8859.
Is it possible or how is it possible to configure the generator to
decode the
Here are some more explanation.
All parameters coming from a form are ISO-8859-1.
The form encoding parameter allows to convert the parameters from
ISO-8859-1 to UTF-8.
And then the parameters are displayed correctly.
Note That the container parameter stays ISO-8859-1.
Then, In my java class, I
You may want to take a look at the wiki page:
http://wiki.apache.org/cocoon/RequestParameterEncoding
I had this problem a while ago:
http://marc.theaimsgroup.com/?l=xml-cocoon-usersm=109100902605917w=2
I'm wondering what the best solution is and which encoding is preferred
for handling special
Jan Hoskens wrote:
You may want to take a look at the wiki page:
http://wiki.apache.org/cocoon/RequestParameterEncoding
I had this problem a while ago:
http://marc.theaimsgroup.com/?l=xml-cocoon-usersm=109100902605917w=2
I'm wondering what the best solution is and which encoding is preferred
I did not know some settings have to be done in web.xml, here is what I
was looking for:
init-param
param-nameform-encoding/param-name
param-valueUTF-8/param-value
/init-param
I uncommented it and now it works
=109100902605917w=2
I'm wondering what the best solution is and which encoding is preferred
for handling special characters or when UTF-8 / ISO 8859-1 should/could
be used.
I can't see any reason why not to use Unicode charset with UTF-8
encoding only. It is supported by all common browsers ans allows you
-cocoon-usersm=109100902605917w=2
I'm wondering what the best solution is and which encoding is
preferred for handling special characters or when UTF-8 / ISO 8859-1
should/could be used.
I can't see any reason why not to use Unicode charset with UTF-8
encoding only. It is supported by all common
Hi,
I've got some encoding problems using the xhtml serializer, I don't
really understand .
(I use Mozilla on Win XP and my editor is set to use UTF-8)
Part 1:
---
I've got the following stylesheet:
--
?xml
FREDERIC MOSER wrote:
Hi,
I've got some encoding problems using the xhtml serializer, I don't
really understand .
(I use Mozilla on Win XP and my editor is set to use UTF-8)
Part 1:
---
I've got the following stylesheet
Hi,
I'm currently facing the following problem: I've set the encoding in my
serializers to ISO-8859-1 and checked the web.xml file (utf-8 is in
comment, defaults to the ISO-8859-1)
Everything is ok (special chars in cforms offer no problem, saving the
document with correct encoding) until I get
set is utf-8. But
in body all of accented char is made by acuted (aacute; ...).
Accented chars In head section is correct, only in body are wrong.
in head:
I have a related problem. I have xsl:output ... encoding=UTF-8 ...
in a stylesheet.
When I run xalan from the command line
there is :
map:serializers default=html
map:serializer name=html mime-type=text/html; charset=utf-8
src=org.apache.cocoon.serialization.HTMLSerializer
encodingutf-8/encoding
omit-xml-declarationtrue/omit-xml-declaration
/map:serializer
/map:serializers
2004. július 22. 08.21 dátummal Upayavira ezt írta:
Have you set the encoding in the definition of your serializer (at the
top of the sitemap)?
yes:
map:serializer name=html mime-type=text/html;
charset=UTF-8
src
Zidarics Zoltan wrote:
2004. július 22. 08.21 dátummal Upayavira ezt írta:
Have you set the encoding in the definition of your serializer (at the
top of the sitemap)?
yes:
map:serializer name=html mime-type=text/html; charset=UTF-8
src
Zidarics Zoltan wrote:
Hi All,
Sorry it doesn't help me :-(
What's the reason for wanting to use HTML serializer (instead of XHTML),
Do you definitely need empty elements like img src=... instead of
img src=... /?
I have also tried several times to get real Unicode characters from HTML
Hi All,
2004. jlius 23. 17.09 dtummal [EMAIL PROTECTED] ezt rta:
What's the reason for wanting to use HTML serializer (instead of
XHTML), Do you definitely need empty elements like img src=...
instead of img src=... /?
I have also tried several times to get real Unicode characters from
HTML
; ...).
Accented chars In head section is correct, only in body are wrong.
in head:
I have a related problem. I have xsl:output ... encoding=UTF-8 ...
in a stylesheet.
When I run xalan from the command line the output is UTF-8.
When I use the sitemap, serialize as xml, it is always ISO-8859-1
; charset=utf-8
src=org.apache.cocoon.serialization.HTMLSerializer
encodingutf-8/encoding
omit-xml-declarationtrue/omit-xml-declaration
/map:serializer
/map:serializers
in web.xml there is:
init-param
param-namecontainer-encoding/param-name
hi
i have try to use sqltransformer with xml files thas have greek content
and i get the error:
Message: SAXException while streaming DOM node to SAX:
org.xml.sax.SAXException: Attempt to output character of integral value
949 that is not represented in specified output encoding of ISO
chars In head section is correct, only in body are wrong.
in head:
I have a related problem. I have xsl:output ... encoding=UTF-8 ...
in a stylesheet.
When I run xalan from the command line the output is UTF-8.
When I use the sitemap, serialize as xml, it is always ISO-8859-1 in the
xml
. But in body all of accented char is made by acuted
(aacute; ...). Accented chars In head section is correct, only
in body are wrong. in head:
I have a related problem. I have xsl:output ... encoding=UTF-8
... in a stylesheet.
When I run xalan from the command line the output is UTF-8.
When I
.
ERROR (2004-07-06) 18:52.25:632 [sitemap.action.mail]
(/mail/mail/mail.wml;jsessionid=1h0hx7bdhgeu2) PoolThread-21/MailAction: Cannot get
store, and
connect
null
This error is seen even after encoding the URL. ie after the session id is embedded in
the url.
Does this mean URLEncoding
, you'll probably
turn up other postings on this topic. I can't remember all the ins
outs, but supposedly the browsers incorrectly supply encoding
information in their requests to Tomcat (ours were POST requests),
and Tomcat by default assumes ISO-8859-1 encoding for the submitted
form data. This gives
Cool, thanks!
Joerg Heinicke [EMAIL PROTECTED]
06/29/2004 09:04 PM
Please respond to users
To:[EMAIL PROTECTED]
cc:
Subject:Re: UTF-8 and Encoding Problems
On 27.06.2004 22:28, Christopher Painter-Wakefield wrote:
I'm not familiar with that setting. Where
I'm not familiar with that setting. Where does it live?
-Christopher
Joerg Heinicke [EMAIL PROTECTED]
06/26/2004 10:27 AM
Please respond to users
To:[EMAIL PROTECTED]
cc:
Subject:Re: UTF-8 and Encoding Problems
On 23.06.2004 23:44, Christopher Painter
On 23.06.2004 23:44, Christopher Painter-Wakefield wrote:
Are you using Tomcat? If you do some searches, you'll probably turn up
other postings on this topic. I can't remember all the ins outs, but
supposedly the browsers incorrectly supply encoding information in their
requests to Tomcat (ours
Here's one I haven't seen before:
I have an HTML form with the following input tag:
input onclick=updateFields(this); name=select value=Patientrsquo;s
Page type=radio
The rsquo; is supposed to translate to this form of the single quote: '
However this string is being stored in the database,
Are you using Tomcat? If you do some searches, you'll probably turn up
other postings on this topic. I can't remember all the ins outs, but
supposedly the browsers incorrectly supply encoding information in their
requests to Tomcat (ours were POST requests), and Tomcat by default assumes
ISO
Quoting Joerg Heinicke [EMAIL PROTECTED]:
On 24.05.2004 15:22, [EMAIL PROTECTED] wrote:
Hi,
how do i encode the parameters in this case :
map:read src=http://foo.com/?p1=v1p2=v2pN=vN/
It's not related to Cocoon, but it is an XML FAQ:
ampersand must be escaped by using the
Hi,
i
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
i
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
how do i encode the parameters in this case :
map:read src=http://foo.com/?p1=v1p2=v2pN=vN/
thanks
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 24.05.2004 15:22, [EMAIL PROTECTED] wrote:
Hi,
how do i encode the parameters in this case :
map:read src=http://foo.com/?p1=v1p2=v2pN=vN/
It's not related to Cocoon, but it is an XML FAQ:
ampersand must be escaped by using the entity amp; (don't use HTML view
to view this mail).
Hi,
How can i generate from an xml file which is ISO-8859-15 encoded?
I've got the following error :
Invalid encoding name ISO-8859-1
thanks in advance
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands
On 27.04.2004 16:07, [EMAIL PROTECTED] wrote:
Hi,
How can i generate from an xml file which is ISO-8859-15 encoded?
I've got the following error :
Invalid encoding name ISO-8859-1
thanks in advance
Is this mismatch ISO-8859-15 and ISO-8859-1 by intent?
Does the old notation ISO8859_1
Joerg Heinicke wrote:
On 27.04.2004 16:07, [EMAIL PROTECTED] wrote:
Hi,
How can i generate from an xml file which is ISO-8859-15 encoded?
I've got the following error :
Invalid encoding name ISO-8859-1
thanks in advance
Is this mismatch ISO-8859-15 and ISO-8859-1 by intent?,
Sorry, i
On Tue, 2004-04-27 at 20:17, defe wrote:
Joerg Heinicke wrote:
On 27.04.2004 16:07, [EMAIL PROTECTED] wrote:
Hi,
How can i generate from an xml file which is ISO-8859-15 encoded?
I've got the following error :
Invalid encoding name ISO-8859-1
thanks in advance
Hi,all:
This's a strange question stuff me up.I set form-encoding to utf-8 in web.xml for
display and submit.I can use this code to get the correct string in Chinese,the form
encoding is utf-8:
userName = new String(request.getParameter(nameField).getBytes(ISO-8859-1
Hi all,
I'm new to I18N and encoding. I've been given a Polish translation,
which I can't read. My resultant HTML pages come out with a meta tag
encoding of UTF-8, but the I18N samples have an encoding of ISO-8859-1.
My page doesn't look right. So:
1) Can anyone tell me what a reasonable
Upayavira [EMAIL PROTECTED] writes:
Hi all,
I'm new to I18N and encoding. I've been given a Polish translation,
which I can't read. My resultant HTML pages come out with a meta tag
encoding of UTF-8, but the I18N samples have an encoding of
ISO-8859-1. My page doesn't look right. So
Martin Holz wrote:
Upayavira [EMAIL PROTECTED] writes:
Hi all,
I'm new to I18N and encoding. I've been given a Polish translation,
which I can't read. My resultant HTML pages come out with a meta tag
encoding of UTF-8, but the I18N samples have an encoding of
ISO-8859-1. My page doesn't look
Iso 8859-1 is not a polish encoding. Use iso 8859-2 which is a common standard or
cp1250 (microsoft codepage - not advised). I write all my polish webapps in utf 8
having no problem at all.
--
Leszek Gawron
lgawronatmobilebox.pl
-Original Message-
From: Upayavira[EMAIL PROTECTED
*Brief Introduction*
There was an extensive discussion about (form) encoding problems using
Cocoon/Jetty/mysql or PostgreSQL, particularly under OS X, obviously
mainly Yves Vindevogel and myself had these problems.
My application is and was running perfectly on Linux with the same
I have no idea ... ;-)
Basically, my problem was solved with a workaround, as described.
I created my database (again) with the latin1 encoding.
When I ask my data with dburl ...?charSet=UTF8, I now get the correct stuff back
I only got this to work with the jdbc2 driver from 7.2 (postgresql
) with the latin1 encoding.
When I ask my data with dburl ...?charSet=UTF8, I now get the correct stuff back
I only got this to work with the jdbc2 driver from 7.2 (postgresql)
I have it working, but I have no clue why.
Anyway, I saw some more mails from the sqltransformer (using byte[] as return)
I still think
IMHO, yes tested with two platforms as server (OSX and Slackware 9) and 3 client platforms (OSX, Linux and the thing from Redmond)
Even stranger: connecting to the same database gave different results depending on the platform Cocoon was running on.
On 08 Apr 2004, at 00:55, Joerg
Joerg Heinicke wrote:
On 08.04.2004 00:33, Alexander Schatten wrote:
My application is and was running perfectly on Linux with the same
configuration, but destroyed all Umlauts after form send on OS X.
Just curious: This is only dependent on the system where the server is
running? And is
:
If tomcat expect the client browser response encoded in UTF-8, but it
receives other encoding, you are in trouble. Looks like some browser
have
fixed ISO-8859-1 as the default encoding and use it to encoded the
response.
I guess this is related to
http://issues.apache.org/bugzilla
section.
Regards
Jorg
Yves Vindevogel wrote:
I mailed with Peter Mount regarding the Encoding problem on OSX.
I found out this
Peter sent me his .jar from version 7.2.
I recompiled my database and did initdb again, this time with
--encoding=latin1
I used his jar, and tested with some dburls
Sure, but ... it's not only OSX related. I had the same problem too on Linux (Slack 9.1)
Seems to be a bug in Postgresql 7.4 (maybe) or my compilation of the driver (now checking)
Anyway, I think it should be put under a topic Cocoon, file encoding and database (jdbc) encoding
I'll create my
Jorg Heymans dijo:
Thank god you finally solved it ! :)
Hi:
Since I don't use MAC OS, I don't opened any related mail until now. :-(
Seems like your solution is no what you desired, because your are not
encoding the database in UTF-8.
In fact this is not a MAC OS problem. You can meet
encoding and database (jdbc) encoding
I'll create my piece of that document. No problem with that.
On 01 Apr 2004, at 14:08, Jorg Heymans wrote:
Thank god you finally solved it ! :)
Seeing how much time you've spent on this (weeks AFAIK), could you wiki this up maybe? I know the end solution shows
Hi,
for what it's worth, while using the following:
OS X 10.3.3
postgreSQL 7.4.1
pg74.1jdbc3.jar (postgreSQL JDBC driver)
Cocoon 2.1.4
Hibernate 2.1.1
I have had absolutely no encoding problems with postgreSQL. Maybe this can be attributed to using Hibernate as my persistence layer
Please send my your .jar and please specify your encoding (in psql\encoding)
I will test this too.
Did you compile yourself or not ?
I also had the problem with SQLTransformer.
On 01 Apr 2004, at 15:12, beyaNet Consultancy wrote:
Hi,
for what it's worth, while using the following:
OS X
in the stylesheet as öäü when the params are
urlencoded.
If there is no urlencoding all characters are correct!
when i use
map:transform src=stylesheets/my.xsl
map:parameter name=myparam value=ÄÜÖ/
/map:transform
all characters are ok.
All our encoding settings are utf-8 (everywhere eg web.xml
of the
request params.
These params apear in the stylesheet as öäü when the params are
urlencoded.
If there is no urlencoding all characters are correct!
IIRC this depends on the stylesheet's encoding and this is the reason
why I would not use it this way.
when i use
map:transform src
On Tue, 2004-03-02 at 20:04, Stefan Geelen wrote:
Hi,
I build a webpage with default charset=ISO-8859-1 encoding.
I need to include another .xml file built in utf-16 encoding:
xi:include href=Example_box.mill parse=text
encoding=UTF-16
xi:fallback
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>
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
On 02.03.2004 20:04, Stefan Geelen wrote:
Hi,
I build a webpage with default charset=ISO-8859-1 encoding.
I need to include another .xml file built in utf-16 encoding:
xi:include href=Example_box.mill parse=text encoding=UTF-16
xi:fallback
pExample
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
Hi Marc,
I am trying to achieve the following:
1. Determine, in my sitemap, whether a browser is XHTML 1.1 compatible. If it is, the XHTML 1.1 serializer is used, which when view sourced in the browser you see:
?xml version=1.0 encoding=UTF-8?>
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.1 /
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
On 27.03.2004 11:26, beyaNet Consultancy wrote:
Hi Marc,
I am trying to achieve the following:
1. Determine, in my sitemap, whether a browser is XHTML 1.1 compatible.
If it is, the XHTML 1.1 serializer is used, which when view sourced in
the browser you see:
?xml version=1.0 encoding=UTF-8
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
Hi,
I am trying to obtain the encoding type as specified in at the top of
my site page when you view source the page. At the moment the encoding
type is specified as:
?xml version=1.0 encoding=UTF-8?
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.1 //EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1.dtd
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
beyaNet Consultancy wrote:
Hi,
I am trying to obtain the encoding type as specified in at the top of my
site page when you view source the page. At the moment the encoding type
is specified as:
?xml version=1.0 encoding=UTF-8?
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.1 //EN
http://www.w3
Marc,
I am using Cocoon version 2.1.4. I have made the changes you mentioned, but nothing has really changed. If I now xsp-request:get-character-encoding> and change the encoding in the page so that it now reads ?xml version=1.0 encoding=ISO-8859-1?> i still only get what is spe
changed. If I now
xsp-request:get-character-encoding and change the encoding in the page
so that it now reads ?xml version=1.0 encoding=ISO-8859-1? i still
only get what is specified in the web.xml document and not in the
web-page. Any ideas?
Peter
On 26 Mar 2004, at 23:08, Marc Portier wrote
context from an XSP page (only interesting code is given here) :
?xml version=1.0 encoding=ISO-8859-1?
xsp:page
login
throwsession:getxml context=temporary
path=/data/throw//throw
/login
/xsp:page
and I use session transformer on the result
?
-Message d'origine-
De : JLM [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 17 mars 2004 16:50
À : [EMAIL PROTECTED]
Objet : Encoding problem
Hello!
I have written a custom authenticator object that sends back to the user an
error message if login fails. So I build a DOM structure
301 - 400 of 565 matches
Mail list logo
