[jira] Updated: (SHALE-456) Tld2Claycfg has problems with encoding
[ https://issues.apache.org/struts/browse/SHALE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Pasierb updated SHALE-456: -- Attachment: encoding.patch the patch seems to solve the problem with encoding Tld2Claycfg has problems with encoding -- Key: SHALE-456 URL: https://issues.apache.org/struts/browse/SHALE-456 Project: Shale Issue Type: Bug Components: Clay Affects Versions: 1.0.4 Environment: windows xp, maven 2.0.7, Reporter: Tom Pasierb Attachments: encoding.patch I'm trying to use Tld2Claycfg tool to convert trinidad, tomahawk and tomahawk tlds to clay config files. In order to do this I've checked out 3 projects, built installed tld2claycfg and mojo projects and configured pom in test project. When I run the mvn clean package goal I the the following exception indicating there's some problem with encoding (all the dependencies were downloaded to my local repo). Is there any config property or system property I should set when running the goal ? The exception is: javax.xml.stream.XMLStreamException: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match. at com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.writeStartDocument(XMLStreamWriterImpl.java:1182) at org.apache.shale.clay.util.TldToClayconfig.writeConfigFile(TldToClayconfig.java:435) at org.apache.shale.clay.util.TldToClayconfig.convert(TldToClayconfig.java:275) ... [ERROR] BUILD FAILURE [INFO] [INFO] !TldToClayconfig.exception: !javax.xml.stream.XMLStreamException: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match.: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match. If you need more info on this, please let me know -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-456) Tld2Claycfg has problems with encoding
[ https://issues.apache.org/struts/browse/SHALE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41508 ] Tom Pasierb commented on SHALE-456: --- I haven't touched the tomahawk jar. To confirm it I deleted whole myfaces directory from my repo. After running mvn package the tomahawk jars were downloaded and I got the same exception. I've also tried tomahawk-sandbox and trinidad each time receiving the same exception. The versions I have tried: trinidad 1.0.1 tomahawk 1.1.6, 1.1.5 tomahawk-sandbox 1.1.6 Apparently the parser opens the file in cp1250 - is there any property it checks? I've tries setting file.encoding system property to utf-8 but that did not help :-( BTW. is myfaces 1.2 and trinidad 1.2.1 supported already? Tld2Claycfg has problems with encoding -- Key: SHALE-456 URL: https://issues.apache.org/struts/browse/SHALE-456 Project: Shale Issue Type: Bug Components: Clay Affects Versions: 1.0.4 Environment: windows xp, maven 2.0.7, Reporter: Tom Pasierb I'm trying to use Tld2Claycfg tool to convert trinidad, tomahawk and tomahawk tlds to clay config files. In order to do this I've checked out 3 projects, built installed tld2claycfg and mojo projects and configured pom in test project. When I run the mvn clean package goal I the the following exception indicating there's some problem with encoding (all the dependencies were downloaded to my local repo). Is there any config property or system property I should set when running the goal ? The exception is: javax.xml.stream.XMLStreamException: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match. at com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.writeStartDocument(XMLStreamWriterImpl.java:1182) at org.apache.shale.clay.util.TldToClayconfig.writeConfigFile(TldToClayconfig.java:435) at org.apache.shale.clay.util.TldToClayconfig.convert(TldToClayconfig.java:275) ... [ERROR] BUILD FAILURE [INFO] [INFO] !TldToClayconfig.exception: !javax.xml.stream.XMLStreamException: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match.: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match. If you need more info on this, please let me know -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-456) Tld2Claycfg has problems with encoding
[ https://issues.apache.org/struts/browse/SHALE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41519 ] Tom Pasierb commented on SHALE-456: --- running the following program: Locale loc = Locale.getDefault(); System.out.println(loc.toString()); System.out.println(---); System.out.println(file.encoding property: + System.getProperty(file.encoding)); System.setProperty(file.encoding, utf-8); // doesn't seem to work String defaultEncoding = new InputStreamReader(new ByteArrayInputStream(new byte[0])).getEncoding(); System.out.println(def encoding: + defaultEncoding); gives the following output: pl_PL --- file.encoding property: Cp1250 def encoding: Cp1250 I've tried setting file.encoding property to utf-8 both programatically and as a system property (using set file.encoding=utf-8 in windows) but that doesn't seem to have any effect. If you expect the files' to be encoded in utf-8 maybe you could pass the encoding to the reading function (if there is such an option). Tld2Claycfg has problems with encoding -- Key: SHALE-456 URL: https://issues.apache.org/struts/browse/SHALE-456 Project: Shale Issue Type: Bug Components: Clay Affects Versions: 1.0.4 Environment: windows xp, maven 2.0.7, Reporter: Tom Pasierb I'm trying to use Tld2Claycfg tool to convert trinidad, tomahawk and tomahawk tlds to clay config files. In order to do this I've checked out 3 projects, built installed tld2claycfg and mojo projects and configured pom in test project. When I run the mvn clean package goal I the the following exception indicating there's some problem with encoding (all the dependencies were downloaded to my local repo). Is there any config property or system property I should set when running the goal ? The exception is: javax.xml.stream.XMLStreamException: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match. at com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.writeStartDocument(XMLStreamWriterImpl.java:1182) at org.apache.shale.clay.util.TldToClayconfig.writeConfigFile(TldToClayconfig.java:435) at org.apache.shale.clay.util.TldToClayconfig.convert(TldToClayconfig.java:275) ... [ERROR] BUILD FAILURE [INFO] [INFO] !TldToClayconfig.exception: !javax.xml.stream.XMLStreamException: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match.: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match. If you need more info on this, please let me know -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SHALE-456) Tld2Claycfg has problems with encoding
Tld2Claycfg has problems with encoding -- Key: SHALE-456 URL: https://issues.apache.org/struts/browse/SHALE-456 Project: Shale Issue Type: Bug Components: Clay Affects Versions: 1.0.4 Environment: windows xp, maven 2.0.7, Reporter: Tom Pasierb I'm trying to use Tld2Claycfg tool to convert trinidad, tomahawk and tomahawk tlds to clay config files. In order to do this I've checked out 3 projects, built installed tld2claycfg and mojo projects and configured pom in test project. When I run the mvn clean package goal I the the following exception indicating there's some problem with encoding (all the dependencies were downloaded to my local repo). Is there any config property or system property I should set when running the goal ? The exception is: javax.xml.stream.XMLStreamException: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match. at com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.writeStartDocument(XMLStreamWriterImpl.java:1182) at org.apache.shale.clay.util.TldToClayconfig.writeConfigFile(TldToClayconfig.java:435) at org.apache.shale.clay.util.TldToClayconfig.convert(TldToClayconfig.java:275) ... [ERROR] BUILD FAILURE [INFO] [INFO] !TldToClayconfig.exception: !javax.xml.stream.XMLStreamException: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match.: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match. If you need more info on this, please let me know -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-316) tomahawk's panelNavigation2 doesn't keep state when navigating between views
[ http://issues.apache.org/struts/browse/SHALE-316?page=comments#action_38633 ] Tom Pasierb commented on SHALE-316: --- [[ Old comment, sent from unregistered email on Sat, 21 Oct 2006 19:37:02 +0200 ]] ok, I missed that. Apparently div all ids should be unique. That also aplies to the pure jsp example. And in all cases I wanted to put content and navigation divs in main div. i'll give it a try. If it still doen't work I'll upload an updated example. -- PS. http://link.interia.pl/f19a6 tomahawk's panelNavigation2 doesn't keep state when navigating between views Key: SHALE-316 URL: http://issues.apache.org/struts/browse/SHALE-316 Project: Shale Issue Type: Bug Components: Clay Affects Versions: 1.0.0, 1.0.1, 1.0.2, 1.0.4-SNAPSHOT, 1.0.3 Environment: tomcat 5.5.17, myfaces 1.1.4, tomahawk 1.1.3, shale 1.0.4-SNAPSHOT Reporter: Tom Pasierb Assigned To: Gary VanMatre Attachments: clayTests-2.zip, clayTests.zip I prepared an example which is attached to the issue entry. Use maven to build the war or exploded app directory and run it. It should start fine. I described briefly what goes wrong and what causes it in my opinion. Basically clay behaves differently if the order in which the panelNavigation2 and symbols are placed in the template file changes. This probably doesn't explain much - just look at the example. I hope that the example I provided will be enough to correct the problem ;-) Regards, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SHALE-316) tomahawk's panelNavigation2 doesn't keep state when navigating between views
[ http://issues.apache.org/struts/browse/SHALE-316?page=comments#action_38480 ] Tom Pasierb commented on SHALE-316: --- I will try it today, thanks. However it would probably still be desirable to make it an issue of Tomahawk's panelNavigation2 - do you think I could just use a part of one of your previous posts as an explanation while creating an issue for this in tomahawk JIRA? Or maybe you could create an issue - you definietly know what you're talking about :-) and I'm just a beginner and don't know all those inner workings of jsf ;-) tomahawk's panelNavigation2 doesn't keep state when navigating between views Key: SHALE-316 URL: http://issues.apache.org/struts/browse/SHALE-316 Project: Shale Issue Type: Bug Components: Clay Affects Versions: 1.0.0, 1.0.1, 1.0.2, 1.0.4-SNAPSHOT, 1.0.3 Environment: tomcat 5.5.17, myfaces 1.1.4, tomahawk 1.1.3, shale 1.0.4-SNAPSHOT Reporter: Tom Pasierb Assigned To: Gary VanMatre Attachments: clayTests-2.zip, clayTests.zip I prepared an example which is attached to the issue entry. Use maven to build the war or exploded app directory and run it. It should start fine. I described briefly what goes wrong and what causes it in my opinion. Basically clay behaves differently if the order in which the panelNavigation2 and symbols are placed in the template file changes. This probably doesn't explain much - just look at the example. I hope that the example I provided will be enough to correct the problem ;-) Regards, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SHALE-316) tomahawk's panelNavigation2 doesn't keep state when navigating between views
[ http://issues.apache.org/struts/browse/SHALE-316?page=all ] Tom Pasierb updated SHALE-316: -- Attachment: clayTests-2.zip an updated version of the example app tomahawk's panelNavigation2 doesn't keep state when navigating between views Key: SHALE-316 URL: http://issues.apache.org/struts/browse/SHALE-316 Project: Shale Issue Type: Bug Components: Clay Affects Versions: 1.0.0, 1.0.1, 1.0.2, 1.0.4-SNAPSHOT, 1.0.3 Environment: tomcat 5.5.17, myfaces 1.1.4, tomahawk 1.1.3, shale 1.0.4-SNAPSHOT Reporter: Tom Pasierb Assigned To: Gary VanMatre Attachments: clayTests-2.zip, clayTests.zip I prepared an example which is attached to the issue entry. Use maven to build the war or exploded app directory and run it. It should start fine. I described briefly what goes wrong and what causes it in my opinion. Basically clay behaves differently if the order in which the panelNavigation2 and symbols are placed in the template file changes. This probably doesn't explain much - just look at the example. I hope that the example I provided will be enough to correct the problem ;-) Regards, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SHALE-316) tomahawk's panelNavigation2 doesn't keep state when navigating between views
tomahawk's panelNavigation2 doesn't keep state when navigating between views Key: SHALE-316 URL: http://issues.apache.org/struts/browse/SHALE-316 Project: Shale Issue Type: Bug Components: Clay Affects Versions: 1.0.3, 1.0.2, 1.0.1, 1.0.0, 1.0.4-SNAPSHOT Environment: tomcat 5.5.17, myfaces 1.1.4, tomahawk 1.1.3, shale 1.0.4-SNAPSHOT Reporter: Tom Pasierb Attachments: clayTests.zip I prepared an example which is attached to the issue entry. Use maven to build the war or exploded app directory and run it. It should start fine. I described briefly what goes wrong and what causes it in my opinion. Basically clay behaves differently if the order in which the panelNavigation2 and symbols are placed in the template file changes. This probably doesn't explain much - just look at the example. I hope that the example I provided will be enough to correct the problem ;-) Regards, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SHALE-292) Clay doesn't consider file's encoding when loading/parsing html templates from hdd
[ http://issues.apache.org/struts/browse/SHALE-292?page=comments#action_38313 ] Tom Pasierb commented on SHALE-292: --- I have tried the updated clay version with html templates. I experimented with -Dfile.encoding (system encoding setting), org.apache.shale.clay.HTML_TEMPLATE_CHARSET context init parameter and -- ### clay:page charset=UTF-8 /### -- and everything works as expected so I guess this issue can be closed. Thanks Gary :-) Clay doesn't consider file's encoding when loading/parsing html templates from hdd -- Key: SHALE-292 URL: http://issues.apache.org/struts/browse/SHALE-292 Project: Shale Issue Type: Bug Components: Clay Affects Versions: 1.0.0, 1.0.1, 1.0.2, 1.0.4-SNAPSHOT, 1.0.3 Environment: windows xp, tomcat 5.5 (started with -Dfile.encoding=UTF-8 option, this way myfaces doesn't convert all non-ascii characters to html entities), myfaces 1.1.3 Reporter: Tom Pasierb Assigned To: Gary VanMatre Attachments: some.html, whatever.jsp Clay reads html files assuming ascii encoding. This way it's impossible to have characters other than ascii in templates. They do not display correctly. As indicated on the user mailing list a Reader object should be used for reading templates instead of InputStream. I wrote more about this on shale user mailing list. We probably need: 1. app wide config option for setting encoding clay should use for reading templates in. Clay would default to this setting unless maybe 2. some per file encoding config option was set (something similar to @page pageEncoding directive for jsps) I marked it as major as this should be corrected if one wants to develop localized applications with non-ascii characters in html templates. As noted by Craig this probably also applies to xml templates, which I haven't tried myself. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
