Issue with Skinning in MyFaces Trinidad
---------------------------------------

                 Key: TRINIDAD-1548
                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1548
             Project: MyFaces Trinidad
          Issue Type: Bug
         Environment: Tomcat 6.x on windows XP, Latest Snapshot release of 
Trinidad 1.2.12 and JSF 1.2, Netbeans 6.7.1, JDK 1.5
            Reporter: sachin walia


I am facing this strange problem where Trinidad is not able to recognize my 
custom CSS skin. 
I've created trinidad-skins.xml and trinidad-config.xml. Both are as below:

trinidad-skins.xml

<?xml version="1.0" encoding="ISO-8859-1"?>
<skins xmlns="http://myfaces.apache.org/trinidad/skin";>
        <skin>
                <id>mobile.default</id>
                <family>default</family>
                <render-kit-id>org.apache.myfaces.trinidad.pda</render-kit-id>
                <style-sheet-name>css/pop.css</style-sheet-name>
        </skin>
</skins>

trinidad-config.xml

<?xml version="1.0" encoding="utf-8"?>
<trinidad-config xmlns="http://myfaces.apache.org/trinidad/config";>
        <skin-family>default</skin-family>
        <debug-output>true</debug-output>
        <client-validation-disabled>true</client-validation-disabled>
</trinidad-config>


the css file is rightfully located in css/pop.css. I also tried using URL as 
/css/pop.css but I am getting following error in any case.

WARNING: Can't find a skin that matches family default and renderkit 
org.apache.myfaces.trinidad.desktop, so we will use the simple skin

Any idea. FYI I don't have any oracle adf components in my WEB-INF/lib. 
Following are the jar files I have in my WEB-INF/lib

commons-beanutils-1.8.0.jar
commons-collections-3.2.jar
commons-digester-2.0.jar
commons-lang-2.3.jar
commons-logging-1.1.jar
jsf-api.jar
jsf-impl.jar
jstl.jar
standard.jar
trinidad-api-1.2.12-SNAPSHOT.jar
trinidad-impl-1.2.12-SNAPSHOT.jar

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to