Hello, back with another encoding problem for which i didn't find an elegant solution yet. i now get different encodings on form fields and filenames from file uploads using the same form.
it i upload files and let turbine process them using the TurbineUploadService, then i'm not able to e.g. get the euro symbol correct in the filename. the umlaut symbols are correct if they appear in filenames. i debugged till the FileUploadBase where the headerEncoding of the MultipartStream is set and there's no problem with that. but the headerEncoding is taken from the FileUploadBase, and the headerEncoding of FileUploadBase is never set. So i think that this never has worked correct... are there any other possibilities to set the encoding, or better get the encoding of the filenames from Content-Disposition headers correct? i think as set by the client if it is the clients task to set this encoding correct? to work around this problem and get a consistent encoding scheme on both the filenames and other form fields i would patch the TurbineUploadService.parseRequest() method to set the headerEncoding of the FileUploadBase(DiskFileUpload) from params.getCharacterEncoding. Mit freundlichen Grüßen / Kind regards, Chris Jölly Unycom Information Technology Services GmbH Solutions for Intellectual Property Management Tel.: +43-316-818 818-30 > -----Ursprüngliche Nachricht----- > Von: Chris Jölly [mailto:[EMAIL PROTECTED] > Gesendet: Dienstag, 17. April 2007 18:27 > An: Turbine Users List > Betreff: AW: Turbine 2.3.2 input encoding > > > Hello! > > jep, some things where severly wrong ;-) > > i missed to also change the jars turbine 2.3.2 depends on. > previously i used 2.3... > > now the initialisation of the inputEncoding seems to work, at least > the log file tells so. :-) > > but now i have another problem on finding the velocity > templates. doe i have also to adjust > some settings in TurbineResources.properties so that they > could be found again? > > the exception which is thrown is: > > 2007-04-17 18:17:33,275 [Thread-13] DEBUG > org.apache.turbine.services.assemblerbroker.util.java.JavaPage > Factory - Class Fragment is Default > 2007-04-17 18:17:33,275 [Thread-13] DEBUG > org.apache.turbine.services.assemblerbroker.util.java.JavaPage > Factory - Trying com.unycom.aportal.modules.pages.Default > 2007-04-17 18:17:33,306 [Thread-13] DEBUG > org.apache.turbine.services.assemblerbroker.util.java.JavaPage > Factory - com.unycom.aportal.modules.pages.Default: Not found > 2007-04-17 18:17:33,306 [Thread-13] DEBUG > org.apache.turbine.services.assemblerbroker.util.java.JavaPage > Factory - Trying org.apache.turbine.flux.modules.pages.Default > 2007-04-17 18:17:33,338 [Thread-13] DEBUG > org.apache.turbine.services.assemblerbroker.util.java.JavaPage > Factory - org.apache.turbine.flux.modules.pages.Default: Not found > 2007-04-17 18:17:33,338 [Thread-13] DEBUG > org.apache.turbine.services.assemblerbroker.util.java.JavaPage > Factory - Trying org.apache.turbine.modules.pages.Default > 2007-04-17 18:17:33,353 [Thread-13] DEBUG > org.apache.turbine.services.assemblerbroker.util.java.JavaPage > Factory - org.apache.turbine.modules.pages.Default: Not found > 2007-04-17 18:17:33,353 [Thread-13] DEBUG > org.apache.turbine.services.assemblerbroker.util.java.JavaPage > Factory - Returning: null > 2007-04-17 18:17:46,135 [Thread-13] ERROR > org.apache.turbine.Turbine - Turbine.handleException: > java.lang.ClassNotFoundException: > > Requested Page not found: Default > Turbine looked in the following modules.packages path: > [com.unycom.aportal.modules, > org.apache.turbine.flux.modules, org.apache.turbine.modules] > > at > org.apache.turbine.modules.PageLoader.getInstance(PageLoader.java:172) > at > org.apache.turbine.modules.PageLoader.exec(PageLoader.java:101) > at org.apache.turbine.Turbine.doGet(Turbine.java:789) > > > > Mit freundlichen Grüßen / Kind regards, > Chris Jölly > Unycom Information Technology Services GmbH > Solutions for Intellectual Property Management > Tel.: +43-316-818 818-30 > > > > > > -----Ursprüngliche Nachricht----- > > Von: Thomas Vandahl [mailto:[EMAIL PROTECTED] > > Gesendet: Montag, 16. April 2007 21:29 > > An: Turbine Users List > > Betreff: Re: Turbine 2.3.2 input encoding > > > > > > 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: [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > 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]
