<Jan 15, 2015 10:09:27 AM COT> <Warning> <org.apache.myfaces.trinidadinternal.skin.SkinFactoryImpl> <BEA-000000> <Cannot find a skin that matches family portal and version v1. We will use the skin portal.desktop.>
This is not a big issue because it does not affect Portal operations, but it makes difficult to track logs and clients have the right to have a free of errors/warnings log.
The solution is described in this post by the A-Team. It is related to the skin version defined in your Portal application, so the recommended action is to delete the skin-version tag in the trinidad-config.xml file.
<?xml version="1.0" encoding="windows-1252"?>
<trinidad-config xmlns="http://myfaces.apache.org/trinidad/config">
<skin-family>#{preferenceBean.defaultTrinidadSkin}</skin-family>
</trinidad-config>
After re-deploying the application the warning message should disappear.
However, apart from that issue, there is another one related to skins:
<Dec 19, 2014 8:09:41 AM COT> <Warning> <org.apache.myfaces.trinidadinternal.skin.SkinCSSDocumentHandler> <BEA-000000> <Not a valid @agent CSS property rule: max-version: 9.0>
<Dec 19, 2014 8:09:41 AM COT> <Warning> <org.apache.myfaces.trinidadinternal.skin.SkinCSSDocumentHandler> <BEA-000000> <Not a valid @agent CSS property rule: max-version: 16.0>
So far, these warnings have no workaround yet. According to an SR I opened with Oracle, it is a benign message and it should be fixed in 11.1.1.9 version.
References
Removing the “Cannot find a skin that matches family portal and version v1.1″ message
Oracle Support Doc ID 1965182.1
ADF BUG 14722194
No comments:
Post a Comment