The Portlet Diagnostic Log Shows Portlet Skin Errors : "Can't find a skin that matches family fusion and renderkit portlet" (Doc ID 1326088.1)

Last updated on JUNE 29, 2017

Applies to:

Oracle WebCenter Portal - Version 11.1.1.2.0 to 11.1.1.3.0 [Release 11g]
Information in this document applies to any platform.
Add ***Checked for relevance on 4-DEC-1012***

Symptoms


The Portlet Diagnostic Log Shows Portlet Skin Errors.

ERROR

[2011-04-26T11:23:18.386-05:00] [WLS_Portlet1] [WARNING] [] [org.apache.myfaces.trinidadinternal.skin.SkinFactoryImpl] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: anonymous] [ecid: 0000IyIbnOJEkJcptgs1yX1DhVno0001nD,0:1:1] [WEBSERVICE_PORT.name: WSRP_v2_Markup_Service] [APP: TestApp] [J2EE_MODULE.name: Polls] [WEBSERVICE.name: WSRP_v2_Service] [J2EE_APP.name: TestApp] Can't find a skin that matches family fusion and renderkit portlet, so we will use the simple skin

[2011-04-26T11:23:18.388-05:00] [WLS_Portlet1] [WARNING] [] [org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderingContext] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: anonymous] [ecid: 0000IyIbnOJEkJcptgs1yX1DhVno0001nD,0:1:1] [WEBSERVICE_PORT.name: WSRP_v2_Markup_Service] [APP: TestApp] [J2EE_MODULE.name: Polls] [WEBSERVICE.name: WSRP_v2_Service] [J2EE_APP.name: TestApp] The skin AppSkin.custom.desktop specified on the requestMap will not be used because it does not exist.

[2011-04-26T11:23:18.389-05:00] [WLS_Portlet1] [WARNING] [] [org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderingContext] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: anonymous] [ecid: 0000IyIbnOJEkJcptgs1yX1DhVno0001nD,0:1:1] [WEBSERVICE_PORT.name: WSRP_v2_Markup_Service] [APP: TestApp] [J2EE_MODULE.name: Polls] [WEBSERVICE.name: WSRP_v2_Service] [J2EE_APP.name: TestApp] The skin simple.portlet specified on the requestMap will be used even though the consumer's skin's styleSheetDocumentId on the requestMap does not match the local skin's styleSheetDocument's id. This will impact performance since the consumer and prodcuer stylesheets cannot be shared. The producer styleclasses will not be compressed to avoid conflicts. A reason the ids do not match may be the jars are not identical on the producer and the consumer. For example, one might have trinidad-skins.xml's skin-additions in a jar file on the class path that the other does not have.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms