ADF Faces and Trinidad renderkits…

Looks like there is a confusion about the renderkits for Trinidad and ADF Faces. Today a colleague asked me what’s up with these renderkit IDs:

  • oracle.adf.core
  • oracle.adf.desktop
  • oracle.adf.pda

The last one ( is the one that you want to use, when running ADF Faces Rich Client (checkout the demo: – However JDeveloper takes care of the faces-config.xml set up.

The first three are legacy IDs from ADF Faces 10g. Once the project was donated to Trinidad the IDs have been changed. When you are running Trinidad, you want to use the (previously oracle.adf.core) in your faces-config.xml file:


If you are interested about ADF Faces 10g to Trinidad migration, checkout this helpful document.


Now these other IDs, used for Skinning, are also now namespaced under the “org.apache.myfaces.trinidad” ID:

  • org.apache.myfaces.trinidad.desktop
  • org.apache.myfaces.trinidad.pda
  • org.apache.myfaces.trinidad.core

So when you now create your own skin, use one of the above to point to a specific RenderKit. A quick example on of doing own skinning for (mobile) Trinidad applications is written here.


Posted in adf, ajax, apache, java, jdeveloper, jsf, jsp, mobile, myfaces, oracle, Oracle ADF Faces, trinidad, web²
One comment on “ADF Faces and Trinidad renderkits…
  1. […] liefert zu den JSF-Standardkomponenten und Trindidad-Basisklassen erweiterte Eigenschaften in folgenden Bereichen, die bei einer Architekturbewertung […]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: