Re: Migration to new version 1.3.3
Oscar, if you grab the quickstart and try to implement simple DB and i18n, what happens - do you get these errors? Rgds Ned Toscano wrote: > > Hello, > > Finally I decided to migrate the project I have been working for the last > year from 1.2.6 to 1.3.3 Wicket version. Some of the errors I got before > are solved, like the AutoComplete field (which is great, by the way), but > I have two issues that I have to solve or I will go back to 1.2.6 for > continuing with the development (we are really in a rush and must go live > this summer). > > The issues are: > - The application is in more than 20 languages, so UTF8 is mandatory. This > was working fine, people types their name in Japanese and that goes to > database smoothly. Now, every "non-english" character gets corrupted. The > database and tomcat server configuration has not been touch, and not the > code except for the migration issues... > > - Suddenly I got stackoverflow exceptions all the time (I have never seen > that with 1.2.6) > > I'm using spring-wicket application with ibatis and postgresql running in > Tomcat 6 with JDK 1.6 > > I have been researching about both in the mailing lists, but I still can't > figure out why this is happening to me... > > As always, thank you very very much for your time and support, > Oskar > > > -- View this message in context: http://www.nabble.com/Migration-to-new-version-1.3.3-tp16820098p16828772.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Migration to new version 1.3.3
> > The issues are: > - The application is in more than 20 languages, so UTF8 is mandatory. This > was working fine, people types their name in Japanese and that goes to > database smoothly. Now, every "non-english" character gets corrupted. The > database and tomcat server configuration has not been touch, and not the > code except for the migration issues... no idea what this is. Wicket is fully UTF-8 by default. > > > - Suddenly I got stackoverflow exceptions all the time (I have never seen > that with 1.2.6) this should be fixed dont know if it made 1.3.3 else you have to use a snapshot or wait for 1.3.4 johan
Migration to new version 1.3.3
Hello, Finally I decided to migrate the project I have been working for the last year from 1.2.6 to 1.3.3 Wicket version. Some of the errors I got before are solved, like the AutoComplete field (which is great, by the way), but I have two issues that I have to solve or I will go back to 1.2.6 for continuing with the development (we are really in a rush and must go live this summer). The issues are: - The application is in more than 20 languages, so UTF8 is mandatory. This was working fine, people types their name in Japanese and that goes to database smoothly. Now, every "non-english" character gets corrupted. The database and tomcat server configuration has not been touch, and not the code except for the migration issues... - Suddenly I got stackoverflow exceptions all the time (I have never seen that with 1.2.6) I'm using spring-wicket application with ibatis and postgresql running in Tomcat 6 with JDK 1.6 I have been researching about both in the mailing lists, but I still can't figure out why this is happening to me... As always, thank you very very much for your time and support, Oskar -- View this message in context: http://www.nabble.com/Migration-to-new-version-1.3.3-tp16820098p16820098.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
