Override TransformerFactory in Weblogic Application Servers

If you have a weird exception like this one while using Oracle Weblogic Application server, this is probably the default Services API of Weblogic is used. To overcome this problem, you could specify your TransformerFactoryImpl in the jvm parameters. If you have xalan*.jar in your classpath, you could provide a jvm parameter as follow:

Create Oracle JDBC Driver as a Module in Wildfly

1. Create a folder under the Wildfly directory:

2. Create a module.xml file in the directory which is created at step 1 and put the content below.

3. Go to the link http://www.oracle.com/technetwork/database/features/jdbc/jdbc-drivers-12c-download-1958347.html and download ojdbc7.jar and put the jar file in the directory which is created at step 1.

4. Go to administration menu of WildFly 8.2 (http://localhost:9990/console/App.html)

5. Navigate to Configuration->Connector->Datasources and then Add a datasource

6. Specify the name of the datasource and JNDI name which should be started with java:/


7. Select the Oracle Database Driver as seen below:

8. Specify the jdbc url, username and password information.

9. Finally datasource is created and you have to enable the datasource. After that to check if the connection is valid or not, you could select the datasource in the same page, and then there is a Test Connection button in the connection tab.

Primefaces Column Toggler (Hide specified columns initially)

Primefaces column toggler component is a helper component of datatable to toggle the visibility of columns. On page load, column chooser finds all columns of datatable and generates the ui at the client side. If toggleable option of a column is set to false, these columns are ignored while generating the ui. However, in some cases if you need a datatable which has huge number of columns, you do not want to show them initially, but you want to give the flexibility to users that they can select the columns they want after initial page load.

From this requirement, I want to prepare an example which is based on the primefaces showcase application. (http://www.primefaces.org/showcase/ui/data/datatable/columnToggler.xhtml) All the backend codes (Car, CarService, CarBean) are the same. The tricky part is at the client side which is stated at the bottom.

ColumnToggler.prototype.render() function of Primefaces is overriden in a way that if columns has a styleClass “not-show-at-start” they will be hidden at the client side.

Overriding the WebLogic JSF libraries Fails With JSF1030

When WebLogic 12.1.2 application overrides the Weblogic JSF libraries with the application’s own provided JSF libraries by using the following directives in an weblogic-application.xml:

Step 1: Add the following Maven dependency to your web application:

Step 2: Then add the following beans.xml to your WEB-INF directory

Weblogic prefer application resources



For this problem we have to edit weblogic.xml according to the configuration below. The prefer-application-packages element specifies a list of packages for classes that must always be loaded from the application. For more information, see prefer-application-packages in Developing Applications for Oracle WebLogic Server.