Hi, Most likely the encoding is broken in the web server (between the browser and your application). I suggest debugging your application.
If you think it is a Jackrabbit problem, could you please create and post a simple, standalone test case that reproduces the problem? It would be great if the test case does not have any dependencies except Jackrabbit (that is, a Java class that uses the JCR API and is run using a static main method). Please include any initialization code, configuration, and the Jackrabbit version you use. Regards, Thomas On Tue, Mar 3, 2009 at 2:09 PM, Kurz Wolfgang <[email protected]> wrote: > Well i was thinking properties. > > Here is the problem I encounter: > > I have a String saved in Jackrabbit under the property Kategorie. > Lets say the string is "Österreich" > > I read that string from jackrabbit and display it on my webpage. > So far all looks fine. > > Now I send that same string right back to my jcr doa to do a query for the > node with the property of that string. > What gets sent to my dao is somehow encoded differently. > The "Ö" becomes some weird symbol. > > If I do the following in my controller everything works fine: > byte[] utf8Bytes = kat.getBytes("ISO-8859-1"); > kat = new String(utf8Bytes, "UTF-8"); > > So I was wondering where the encoding goes wrong. > > Thx again. > > > > -----Ursprüngliche Nachricht----- > Von: Julian Reschke [mailto:[email protected]] > Gesendet: Dienstag, 3. März 2009 14:01 > An: [email protected] > Betreff: Re: Jackrabbit encoding > > Kurz Wolfgang wrote: >> Is there a way to set the encoding for Jackrabbit so all the content is >> UTF-8 encoded? >> >> Thx in advance:-) > > Exactly what content? Node names? Properties other than binary properties? > > BR, Julian > >
