[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5639) Previewer doesn't support internationalization

[ https://jira.jboss.org/jira/browse/JBIDE-5639?page=com.atlassian.jira.plu... ] Denis Maliarevich commented on JBIDE-5639: ------------------------------------------ After some debugging I think I found the reason. When JBDS processes faces-config.xml file it could be considered as on ordinary XML file or as a JSF configuration XML file. And if faces-config is treated as JSF configuration file resource bundles are loaded correctly. On the other hand if faces-config is recognized as a simple xml - bundles aren't loaded. Different recognition happens because of the different xml file's header. At appeares that JBDS understands well such headers as: <?xml version="1.0" encoding="UTF-8"?> <faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd"> and the following says nothing to it: <?xml version="1.0"?> <faces-config xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd" version="2.0"> I'll check the mechanism of the faces-config.xml loading in the code to find the concrete reason. But for now it could be connected with JBIDE-5642 where there was the similar problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira