You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by da...@continentale.de on 2007/08/09 10:44:59 UTC
Bug in trinidad-1.0.2-SNAPSHOT with German umlauts and facelets?
Hi,
i've probably found a bug with german umlauts and PPR in trinidad
1.0.2-SNAPSHOT in combination with facelets.
After a PPR-Request within a panelTabbed the submitted values, which contains
german umlauts, are broken. The encoding of the xhtml-file ist ISO-8859-1,
even to support values with german umlauts there. The initial result of my
example-page is all right.
I've tested in the following environment:
- trinidad-api, trinidad-impl - 1.0.2-SNAPSHOT
- myfaces-api, myfaces-impl - 1.1.6-SNAPSHOT
- jsf-facelets - 1.1.12
- jetty - 6.1.3
(- Firefox 2, IE 6)
Here is my example-page:
<?xml version="1.0" encoding="ISO-8859-1"?>
<trh:html xmlns:trh="http://myfaces.apache.org/trinidad/html"
xmlns:tr="http://myfaces.apache.org/trinidad">
<trh:head>
<title>PPR-Bug in 1.0.2-SNAPSHOT?</title>
</trh:head>
<trh:body>
<tr:form>
<tr:panelTabbed position="above">
<tr:showDetailItem text="tab 1">
<tr:inputText label="inputText tab 1"
value="ä"></tr:inputText>
</tr:showDetailItem>
<tr:showDetailItem text="tab 2">
<tr:inputText label="inputText tab 2"
value=""></tr:inputText>
</tr:showDetailItem>
</tr:panelTabbed>
</tr:form>
</trh:body>
</trh:html>
There are no such problems with trinidad 1.0.1 artefacts.
Greetings
Daniel
Re: Bug in trinidad-1.0.2-SNAPSHOT with German umlauts and
facelets?
Posted by Daniel Niklas <da...@continentale.de>.
Hi,
> This is a bug in Netbeans for Windows (perhaps java), in linux you don't
> have this kind of error. It looks like in windows UTF-8 is not handled
> very well.
I don't use Netbeans.
My environment ist Windows 2000 SP4 and
- trinidad-api, trinidad-impl - 1.0.2-SNAPSHOT
- myfaces-api, myfaces-impl - 1.1.6-SNAPSHOT
- jsf-facelets - 1.1.12
- jetty - 6.1.3
(- Firefox 2, IE 6)
Daniel
--
View this message in context: http://www.nabble.com/Bug-in-trinidad-1.0.2-SNAPSHOT-with-German-umlauts-and-facelets--tf4242728.html#a12090804
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: Bug in trinidad-1.0.2-SNAPSHOT with German umlauts and facelets?
Posted by Luka Surija <lu...@iytim.hr>.
Daniel Niklas wrote:
> Hi Adam,
>
>
>> Alright, fixed on trunk. I'll try to make sure this gets into the
>> official 1.0.2 release.
>>
> Thanks a lot for fixing this so fast!
>
>
>> I can definitely say that I STRONGLY recommend web
>> developers use UTF-8, and abandon all the old
>> character sets.
>>
> Good point, i would like to use UTF-8 encoding, but i got errors
> whith this encoding, when the file contains an umlaut:
> "Error Parsing /ppr-bug.xhtml: Error Traced[line: 15] Invalid byte 2 of
> 3-byte UTF-8 sequence."
> This is the line within an "ä".
>
This is a bug in Netbeans for Windows (perhaps java), in linux you don't
have this kind of error. It looks like in windows UTF-8 is not handled
very well.
> Can you give me a hint, how to do this correct?
>
> Regards
> Daniel :-)
>
> Stack Trace:
>
> com.sun.facelets.FaceletException: Error Parsing /ppr-bug.xhtml: Error
> Traced[line: 15] Invalid byte 2 of 3-byte UTF-8 sequence.
> at com.sun.facelets.compiler.SAXCompiler.doCompile(SAXCompiler.java:234)
> at com.sun.facelets.compiler.Compiler.compile(Compiler.java:105)
> at
> com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:197)
> at
> com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:144)
> at
> com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:95)
> at
> com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:496)
> at
> com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:546)
> at
> org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:182)
> at
> org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
> at
> org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:138)
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:141)
> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1098)
> at
> org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:241)
> at
> org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:198)
> at
> org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:152)
> at
> org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089)
> at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
> at org.mortbay.jetty.Server.handle(Server.java:285)
> at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:502)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:821)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:208)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:378)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:368)
> at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
>
Re: Bug in trinidad-1.0.2-SNAPSHOT with German umlauts and
facelets?
Posted by Daniel Niklas <da...@continentale.de>.
Hi,
> I think I saw this a while ago, using facelets.
> Can you try a *single* page, that contains
Something like this?
<?xml version="1.0" encoding="UTF-8"?>
<trh:html xmlns:trh="http://myfaces.apache.org/trinidad/html"
xmlns:tr="http://myfaces.apache.org/trinidad">
<trh:head>
<title>problem with umlauts</title>
</trh:head>
<trh:body>
<h1>umlaut-problem</h1>
<p>ääää üüüüüü</p>
</trh:body>
</trh:html>
(causes error "Invalid byte 2 of 3-byte UTF-8 sequence.")
Daniel
--
View this message in context: http://www.nabble.com/Bug-in-trinidad-1.0.2-SNAPSHOT-with-German-umlauts-and-facelets--tf4242728.html#a12089649
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: Bug in trinidad-1.0.2-SNAPSHOT with German umlauts and facelets?
Posted by Matthias Wessendorf <ma...@apache.org>.
däh,
I think I saw this a while ago, using facelets.
Can you try a *single* page, that contains
ääää üüüüüü etc ?
-M
On 8/10/07, Daniel Niklas <da...@continentale.de> wrote:
>
> Hi Adam,
>
> > Alright, fixed on trunk. I'll try to make sure this gets into the
> > official 1.0.2 release.
> Thanks a lot for fixing this so fast!
>
> > I can definitely say that I STRONGLY recommend web
> > developers use UTF-8, and abandon all the old
> > character sets.
> Good point, i would like to use UTF-8 encoding, but i got errors
> whith this encoding, when the file contains an umlaut:
> "Error Parsing /ppr-bug.xhtml: Error Traced[line: 15] Invalid byte 2 of
> 3-byte UTF-8 sequence."
> This is the line within an "ä".
>
> Can you give me a hint, how to do this correct?
>
> Regards
> Daniel :-)
>
> Stack Trace:
>
> com.sun.facelets.FaceletException: Error Parsing /ppr-bug.xhtml: Error
> Traced[line: 15] Invalid byte 2 of 3-byte UTF-8 sequence.
> at com.sun.facelets.compiler.SAXCompiler.doCompile(SAXCompiler.java:234)
> at com.sun.facelets.compiler.Compiler.compile(Compiler.java:105)
> at
> com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:197)
> at
> com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:144)
> at
> com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:95)
> at
> com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:496)
> at
> com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:546)
> at
> org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:182)
> at
> org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
> at
> org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:138)
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:141)
> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1098)
> at
> org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:241)
> at
> org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:198)
> at
> org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:152)
> at
> org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089)
> at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
> at org.mortbay.jetty.Server.handle(Server.java:285)
> at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:502)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:821)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:208)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:378)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:368)
> at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
> --
> View this message in context: http://www.nabble.com/Bug-in-trinidad-1.0.2-SNAPSHOT-with-German-umlauts-and-facelets--tf4242728.html#a12088181
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
Re: Bug in trinidad-1.0.2-SNAPSHOT with German umlauts and facelets?
Posted by Adam Winer <aw...@gmail.com>.
You seem to be confusing two different concepts:
- the encoding of the XML file handed to Facelets
- the encoding of the HTML file send to the browser
I forget how Facelets defaults its encoding, but these two
do not need to be the same. The error you're seeing
here is that you've typed your file in ISO-8859-1,
and then switched the encoding to claim its UTF-8,
which is false. I'm talking about setting the contentType
to use a UTF-8 character set on the HTML generated.
-- Adam
On 8/10/07, Daniel Niklas <da...@continentale.de> wrote:
>
> Hi Adam,
>
> > Alright, fixed on trunk. I'll try to make sure this gets into the
> > official 1.0.2 release.
> Thanks a lot for fixing this so fast!
>
> > I can definitely say that I STRONGLY recommend web
> > developers use UTF-8, and abandon all the old
> > character sets.
> Good point, i would like to use UTF-8 encoding, but i got errors
> whith this encoding, when the file contains an umlaut:
> "Error Parsing /ppr-bug.xhtml: Error Traced[line: 15] Invalid byte 2 of
> 3-byte UTF-8 sequence."
> This is the line within an "ä".
>
> Can you give me a hint, how to do this correct?
>
> Regards
> Daniel :-)
>
> Stack Trace:
>
> com.sun.facelets.FaceletException: Error Parsing /ppr-bug.xhtml: Error
> Traced[line: 15] Invalid byte 2 of 3-byte UTF-8 sequence.
> at com.sun.facelets.compiler.SAXCompiler.doCompile(SAXCompiler.java:234)
> at com.sun.facelets.compiler.Compiler.compile(Compiler.java:105)
> at
> com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:197)
> at
> com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:144)
> at
> com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:95)
> at
> com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:496)
> at
> com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:546)
> at
> org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:182)
> at
> org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
> at
> org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:138)
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:141)
> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1098)
> at
> org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:241)
> at
> org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:198)
> at
> org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:152)
> at
> org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089)
> at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
> at org.mortbay.jetty.Server.handle(Server.java:285)
> at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:502)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:821)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:208)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:378)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:368)
> at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
> --
> View this message in context: http://www.nabble.com/Bug-in-trinidad-1.0.2-SNAPSHOT-with-German-umlauts-and-facelets--tf4242728.html#a12088181
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>
Re: Bug in trinidad-1.0.2-SNAPSHOT with German umlauts and
facelets?
Posted by Daniel Niklas <da...@continentale.de>.
Hi Adam,
> Alright, fixed on trunk. I'll try to make sure this gets into the
> official 1.0.2 release.
Thanks a lot for fixing this so fast!
> I can definitely say that I STRONGLY recommend web
> developers use UTF-8, and abandon all the old
> character sets.
Good point, i would like to use UTF-8 encoding, but i got errors
whith this encoding, when the file contains an umlaut:
"Error Parsing /ppr-bug.xhtml: Error Traced[line: 15] Invalid byte 2 of
3-byte UTF-8 sequence."
This is the line within an "ä".
Can you give me a hint, how to do this correct?
Regards
Daniel :-)
Stack Trace:
com.sun.facelets.FaceletException: Error Parsing /ppr-bug.xhtml: Error
Traced[line: 15] Invalid byte 2 of 3-byte UTF-8 sequence.
at com.sun.facelets.compiler.SAXCompiler.doCompile(SAXCompiler.java:234)
at com.sun.facelets.compiler.Compiler.compile(Compiler.java:105)
at
com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:197)
at
com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:144)
at
com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:95)
at
com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:496)
at
com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:546)
at
org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:182)
at
org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
at
org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:138)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:141)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1098)
at
org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:241)
at
org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:198)
at
org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:152)
at
org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:285)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:502)
at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:821)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:208)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:378)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:368)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
--
View this message in context: http://www.nabble.com/Bug-in-trinidad-1.0.2-SNAPSHOT-with-German-umlauts-and-facelets--tf4242728.html#a12088181
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: Bug in trinidad-1.0.2-SNAPSHOT with German umlauts and facelets?
Posted by Adam Winer <aw...@gmail.com>.
Alright, fixed on trunk. I'll try to make sure this gets into the
official 1.0.2 release.
-- Adam
On 8/9/07, Adam Winer <aw...@gmail.com> wrote:
> What I've found in early testing is that:
> - Everything works fine if your page is in UTF-8
> - In ISO-8859-1, the very first request is handled poorly; subsequent
> requests seem to work fine
>
> I know that XMLHttp requests are *always* delivered as UTF-8,
> and this is likely the issue here - the characters are being
> sent as UTF-8 from the browser, but interpreted as ISO-8859-1
> on the server.
>
> I can definitely say that I STRONGLY recommend web
> developers use UTF-8, and abandon all the old
> character sets. Not just my advice, that's advice given
> in general. Still, this should work and I'll give fixing it a whirl.
>
> -- Adam
>
>
>
> On 8/9/07, Adam Winer <aw...@gmail.com> wrote:
> > I'll try to have a look at this today (this'd be an important
> > bug to nail before releasing 1.0.2.)
> >
> > -- Adam
> >
> >
> > On 8/9/07, daniel.niklas@continentale.de <da...@continentale.de> wrote:
> > > Hi,
> > >
> > > i've probably found a bug with german umlauts and PPR in trinidad
> > > 1.0.2-SNAPSHOT in combination with facelets.
> > > After a PPR-Request within a panelTabbed the submitted values, which contains
> > > german umlauts, are broken. The encoding of the xhtml-file ist ISO-8859-1,
> > > even to support values with german umlauts there. The initial result of my
> > > example-page is all right.
> > >
> > > I've tested in the following environment:
> > > - trinidad-api, trinidad-impl - 1.0.2-SNAPSHOT
> > > - myfaces-api, myfaces-impl - 1.1.6-SNAPSHOT
> > > - jsf-facelets - 1.1.12
> > > - jetty - 6.1.3
> > > (- Firefox 2, IE 6)
> > >
> > > Here is my example-page:
> > >
> > > <?xml version="1.0" encoding="ISO-8859-1"?>
> > > <trh:html xmlns:trh="http://myfaces.apache.org/trinidad/html"
> > > xmlns:tr="http://myfaces.apache.org/trinidad">
> > >
> > > <trh:head>
> > > <title>PPR-Bug in 1.0.2-SNAPSHOT?</title>
> > > </trh:head>
> > > <trh:body>
> > >
> > > <tr:form>
> > >
> > > <tr:panelTabbed position="above">
> > > <tr:showDetailItem text="tab 1">
> > > <tr:inputText label="inputText tab 1"
> > > value="ä"></tr:inputText>
> > > </tr:showDetailItem>
> > > <tr:showDetailItem text="tab 2">
> > > <tr:inputText label="inputText tab 2"
> > > value=""></tr:inputText>
> > > </tr:showDetailItem>
> > > </tr:panelTabbed>
> > >
> > > </tr:form>
> > >
> > > </trh:body>
> > > </trh:html>
> > >
> > > There are no such problems with trinidad 1.0.1 artefacts.
> > >
> > > Greetings
> > > Daniel
> > >
> >
>
Re: Bug in trinidad-1.0.2-SNAPSHOT with German umlauts and facelets?
Posted by Adam Winer <aw...@gmail.com>.
What I've found in early testing is that:
- Everything works fine if your page is in UTF-8
- In ISO-8859-1, the very first request is handled poorly; subsequent
requests seem to work fine
I know that XMLHttp requests are *always* delivered as UTF-8,
and this is likely the issue here - the characters are being
sent as UTF-8 from the browser, but interpreted as ISO-8859-1
on the server.
I can definitely say that I STRONGLY recommend web
developers use UTF-8, and abandon all the old
character sets. Not just my advice, that's advice given
in general. Still, this should work and I'll give fixing it a whirl.
-- Adam
On 8/9/07, Adam Winer <aw...@gmail.com> wrote:
> I'll try to have a look at this today (this'd be an important
> bug to nail before releasing 1.0.2.)
>
> -- Adam
>
>
> On 8/9/07, daniel.niklas@continentale.de <da...@continentale.de> wrote:
> > Hi,
> >
> > i've probably found a bug with german umlauts and PPR in trinidad
> > 1.0.2-SNAPSHOT in combination with facelets.
> > After a PPR-Request within a panelTabbed the submitted values, which contains
> > german umlauts, are broken. The encoding of the xhtml-file ist ISO-8859-1,
> > even to support values with german umlauts there. The initial result of my
> > example-page is all right.
> >
> > I've tested in the following environment:
> > - trinidad-api, trinidad-impl - 1.0.2-SNAPSHOT
> > - myfaces-api, myfaces-impl - 1.1.6-SNAPSHOT
> > - jsf-facelets - 1.1.12
> > - jetty - 6.1.3
> > (- Firefox 2, IE 6)
> >
> > Here is my example-page:
> >
> > <?xml version="1.0" encoding="ISO-8859-1"?>
> > <trh:html xmlns:trh="http://myfaces.apache.org/trinidad/html"
> > xmlns:tr="http://myfaces.apache.org/trinidad">
> >
> > <trh:head>
> > <title>PPR-Bug in 1.0.2-SNAPSHOT?</title>
> > </trh:head>
> > <trh:body>
> >
> > <tr:form>
> >
> > <tr:panelTabbed position="above">
> > <tr:showDetailItem text="tab 1">
> > <tr:inputText label="inputText tab 1"
> > value="ä"></tr:inputText>
> > </tr:showDetailItem>
> > <tr:showDetailItem text="tab 2">
> > <tr:inputText label="inputText tab 2"
> > value=""></tr:inputText>
> > </tr:showDetailItem>
> > </tr:panelTabbed>
> >
> > </tr:form>
> >
> > </trh:body>
> > </trh:html>
> >
> > There are no such problems with trinidad 1.0.1 artefacts.
> >
> > Greetings
> > Daniel
> >
>
Re: Bug in trinidad-1.0.2-SNAPSHOT with German umlauts and facelets?
Posted by Adam Winer <aw...@gmail.com>.
I'll try to have a look at this today (this'd be an important
bug to nail before releasing 1.0.2.)
-- Adam
On 8/9/07, daniel.niklas@continentale.de <da...@continentale.de> wrote:
> Hi,
>
> i've probably found a bug with german umlauts and PPR in trinidad
> 1.0.2-SNAPSHOT in combination with facelets.
> After a PPR-Request within a panelTabbed the submitted values, which contains
> german umlauts, are broken. The encoding of the xhtml-file ist ISO-8859-1,
> even to support values with german umlauts there. The initial result of my
> example-page is all right.
>
> I've tested in the following environment:
> - trinidad-api, trinidad-impl - 1.0.2-SNAPSHOT
> - myfaces-api, myfaces-impl - 1.1.6-SNAPSHOT
> - jsf-facelets - 1.1.12
> - jetty - 6.1.3
> (- Firefox 2, IE 6)
>
> Here is my example-page:
>
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <trh:html xmlns:trh="http://myfaces.apache.org/trinidad/html"
> xmlns:tr="http://myfaces.apache.org/trinidad">
>
> <trh:head>
> <title>PPR-Bug in 1.0.2-SNAPSHOT?</title>
> </trh:head>
> <trh:body>
>
> <tr:form>
>
> <tr:panelTabbed position="above">
> <tr:showDetailItem text="tab 1">
> <tr:inputText label="inputText tab 1"
> value="ä"></tr:inputText>
> </tr:showDetailItem>
> <tr:showDetailItem text="tab 2">
> <tr:inputText label="inputText tab 2"
> value=""></tr:inputText>
> </tr:showDetailItem>
> </tr:panelTabbed>
>
> </tr:form>
>
> </trh:body>
> </trh:html>
>
> There are no such problems with trinidad 1.0.1 artefacts.
>
> Greetings
> Daniel
>