Running RichFaces 4.1.0.Final on WebLogic 12c

Markus Eisele
You might have noticed, that I simply love JSF. Not only the specification and the reference implementation Mojarra but also the most creative component suites on the market. This is my all-time favorite PrimeFaces and of course RichFaces. This is the reason why you find "running xxx on xxx" posts here :) Today is my RichFaces and WebLogic day, so a little followup on my earlier post this is more an update on how to get it running on latest WebLogic 12c. Here we go:

Download the IDE of your choice. I will use NetBeans 7.1 RC 2 for this post. Download and install WebLogic Server 12c. Either with the platform installer of your choice or from the ZIP distribution. Go on with creating a domain and adding the server to NetBeans. (For more details see my earlier post.) Go back to NetBeans, check your maven settings and create a new Maven Web Application project. Let's call it rfshowcase for now. Enter the missing stuff (Group, Version and Package). Select or add your local Oracle WebLogic server as your runtime environment. Add the JBoss Maven repository and the magic richfaces-bom to your pom.xml:

 <name>JBoss Repository</name> 

 <!-- ... -->

<!-- ... -->

Add the RichFaces dependencies:



And you are done! Unlike with earlier version of WLS (compare my older post) JSF 2.x and JSTL 1.2 have been incorporated directly into the server's classpath. Applications deployed to WebLogic Server can seamlessly make use of JSF 2.x and JSTL 1.2 without requiring developers to deploy and reference separate shared libraries. So, you can actually start implementing your application.

Some simple tests
Let's go and add an index.xhtml to your Web Pages folder. Add the RichFaces namespaces to your html tag:

xmlns:a4j="" xmlns:rich=""

And start using your needed components. In my little example I stripped down the rich:panelMenu taken from the . Now right click on your project and "Run" it! NetBeans is starting your WLS instance and deploys your application. After this is done it should open a browser which points you to http://localhost:7001/rfshowcase/ and you see your application up and running. That's all. Nothing more to do. No library deployment, nothing else. That's what I would call a good progress. Compared to the stupid library deployment that was needed with earlier versions of WLS you know have the freedom to use whatever comes your way. Even if you feel like using another RI you could simply revert the classloader by specifying the prefer-application-packages tag in your weblogic.xml

13.12.2011 20:48:43 org.richfaces.application.InitializationListener onStart
INFO: RichFaces Core Implementation by JBoss, a division of Red Hat, Inc., version v.4.1.0.Final

Clazzloading or Oracle and RedHat vs. Google
If you look at your application from a classloader point of view you will see, that you have a good number (705) of classes in conflict. In the case of RichFaces all these are in the* package. The reason for that is, that WLS is distributing a which conflicts with the RichFaces dependency Running my small tests this doesn't seem to do any harm at all. But it would be best to configure a so called FilteringClassLoader which provides a mechanism for you to configure deployment descriptors to explicitly specify that certain packages should always be loaded from the application, rather than being loaded by the system classloader. So you should change your project to be an EAR module and add this little paragraph to your weblogic-application.xml (ear level):

Post a Comment


  1. Great post Markus! I'm sure the tidbit about filtering the guava classes will be usefult to many - but why not just exclude the guava maven dependency in your pom?

  2. Hi Brian,

    Thanks for your comment. Guave was introduced by the rf dependencies. I would never think about removing it when it gets introduced by a framework. Anyway, thanks for the comment and for clarifying that it's a not neede dependency.


  3. Sorry to mislead - it is indeed a needed dependency; but if your application server is providing it, you could exclude it (JBoss AS 7 for instance let's you expose internal libraries to applications with a entry).

    Looking more closely however, you mention the guava versions involved, and they are too disparate for that to work in this case...

Post a Comment