Hello Joerg,
Thank you for your reply.
No, the XML declaration is hard coded in the specified JSP (the one you can
see in the pipline definition).
The interesting thing is that when I display a xml document with a pipline
like this one
<map:match pattern="JAVA.Login_Screen">
<map:generate
src="/maxess/Xplorer/jsp/Screens/Login_Screen_JAVA.xml"/>
<map:serialize type="xml"/>
</map:match>
(hence displaying a static xml document) it works fine. But when generating
the xml with the jsp generator
it doesn't work properly. So I think the problem lies in the jsp generator.
Any hints for that kind of problem?
As I observe several other people using cocoon have problems with umlaut
since version 2.02. But so far I haven't
found a solution for that problem.
With best regards
Frank
-----Urspr�ngliche Nachricht-----
Von: Joerg Heinicke [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 3. Juni 2003 21:15
An: [EMAIL PROTECTED]
Betreff: Re: Problems with umlaut in cocoon2.04
Hello Frank,
are you generating the XML declaration (<?xml version="1.0"
encoding="ISO-8859-1"?>) by hand (so as string) or via some XML methods
or tags?
Joerg
Przybilla, Frank wrote:
> Hello Cocoon community,
>
> I hope there is somebody out there who can explain me the following:
>
> I'm using cocoon 2.0.4 together with tomcat.1.4.24 and jdk1.41 and I have
> the following szenario, which
> worked well with cocoon 2.01, tomcat4.0 and jdk1.3.x.
>
> In this szenario I have a jsp which generates an xml document which
includes
> characters like �,�,�,� etc.
> Therfore I specify <?xml version="1.0" encoding="ISO-8859-1"?>.
Additionally
> I'm using the folowing pipline
> definition in the sitemap:
>
> <map:match pattern="JAVA.Login_Screen">
> <map:generate type="jsp"
> src="/maxess/Xplorer/jsp/Screens/Login_Screen_JAVA.jsp"/>
> <map:serialize type="xml"/>
> </map:match>
>
> So I'm using a jsp generator which dynamically generates the xml. I also
set
> the correct ecoding for the xml serializier component (ISO-8859-1).
> But with cocoon 2.04 the output is not correct, because the umlaut is not
> correctly encoded and presented . As I mentioned before, everything
> works fine with cocoon2.01. What must be changed so that the encoding is
> correct?
>
>
> With best regards
>
> Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
