Re: Re: Tapestry output changes from Tomcat to JBoss

2006-11-21 Thread Sam Gendler
I'll second that solution. Unless you tell the VM what the default file encoding should be, you have to explicitly tell every single stream you read or write data from that it should use UTF-8 encoding, assuming that UTF-8 isn't the default encoding on your system. I have found that the default

Tapestry output changes from Tomcat to JBoss

2006-11-21 Thread Jan Normann Nielsen
Hello I've tried two forums, but noone has had an answer. Now I try this mailing list instead. I'm experiencing a strange problem. When deploying my Tapestry 4 application directly in Tomcat 5.5.20, it runs perfectly, and my localized messages (rendered using span key=...) are output as