You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Chris Jölly <ch...@unycom.com> on 2007/04/16 18:54:31 UTC

Turbine 2.3.2 input encoding

Hello!
 
i want to set the input encoding of the webapp using 2.3.2 to something other then 
US-ASCII.
 
the parameter input.encoding from TurbineResources.properties is completely ignored.
 
so i looked at the code and debugged the Turbine.configure method to see whats
happening. at the line around:
 
        // Initialize the service manager. Services
        // that have its 'earlyInit' property set to
        // a value of 'true' will be started when
        // the service manager is initialized.
        getServiceManager().init();
 
        // Get the default input encoding
        inputEncoding = configuration.getString(
                TurbineConstants.PARAMETER_ENCODING_KEY,
                TurbineConstants.PARAMETER_ENCODING_DEFAULT);
 
there are 'strange' things happening. the line setting the inputEncoding is never executed,
therefore the inputEncoding remains null. During a Turbine.doGet() call if the request has
no character encoding set Turbine wants to set the encoding to null which results in an 
exception...
 
now my questions is: how can i set the character encoding in turbine 2.3.2?
 
thx.

Mit freundlichen Grüßen / Kind regards, 
________________________________

Chris Jölly

 

Unycom Information Technology Services GmbH

Solutions for Intellectual Property Management

 

Schmiedlstrasse 1 / III, 8042 Graz / Austria

Tel.: +43-316-818 828-30
Fax: +43-316-818 818-38

E-Mail: chris.joelly@unycom.com 
Web:  <blocked::http://www.unycom.com/> www.unycom.com 

Firmenbuch Nr: FN 203321b / LG Graz

UID Nr.: ATU 50837803
________________________________ 

 

Re: Turbine 2.3.2 input encoding

Posted by Thomas UNG <th...@gmail.com>.
I went through this problem when setting up my platform

I am not sure what I did.. But did you try the following:

services.VelocityService.input.encoding                            =UTF-8

database.url.extension                                             =
useUnicode=true&characterEncoding=utf8

input.encoding                                                     = UTF-8
locale.default.charset                                             = UTF-8


That's only what I got in my TR.properties and I have a working UTF-8 instance.

Regards,
Thomas

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org


Re: Turbine 2.3.2 input encoding

Posted by Thomas Vandahl <tv...@apache.org>.
Chris Jölly wrote:
>         // Get the default input encoding
>         inputEncoding = configuration.getString(
>                 TurbineConstants.PARAMETER_ENCODING_KEY,
>                 TurbineConstants.PARAMETER_ENCODING_DEFAULT);
>  
> there are 'strange' things happening. the line setting the inputEncoding is never executed,

If that is the case, some things are severely wrong. What does your
turbine.log tell you (maybe in debug mode)? We've got Turbine working
with ISO-8859-1 encoding just fine.


Bye, Thomas

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org