Change the default target to archive (we aren't going to cover automatic deployment to OC4J).

<project name="oc4j_example" default="archive" basedir=".">

OC4J looks for the drools file /security.drl file in the root of the war file instead of the root of the ear file so we need to have the build.xml move it to the correct location at build time. The following must be added at the top of the <target name="war" depends="compile" description="Build the distribution .war file"> target.

<copy todir="${war.dir}">
 <fileset dir="${basedir}/resources" >
    <include name="*.drl" />
 </fileset>
 </copy>

Alter the jta-data-source to be jdbc/__oc4jexample (and use this as the jndi-name when creating the data source in data-sources.xml later during deployment).

Add the properties (described in jee5/booking example):

<property name="hibernate.query.factory_class"
   value="org.hibernate.hql.classic.ClassicQueryTranslatorFactory" />
<property name="hibernate.transaction.manager_lookup_class"
   value="org.hibernate.transaction.OrionTransactionManagerLookup" />
<property name="hibernate.transaction.flush_before_completion" 
   value="true"/>
<property name="hibernate.cache.provider_class" 
   value="org.hibernate.cache.HashtableCacheProvider"/>

Remove the JBoss AS specific method of exposing the EntityManagerFactory:

<property 
 name="jboss.entity.manager.factory.jndi.name" 
 value="java:/oc4j_exampleEntityManagerFactory">

You'll need to alter persistence-prod.xml as well if you want to deploy to OC4J using the prod profile.

Enable container managed transaction integration - add the <transaction:ejb-transaction /> component, and it's namespace declaration xmlns:transaction="http://jboss.com/products/seam/transaction"

Alter the jndi-pattern to java:comp/env/oc4j_example/#{ejbName}/local

We want to use a Seam Managed Persistence Context in our application. Unfortunately OC4J doesn't expose the EntityManagerFactory in JNDI, but Seam provides a built-in manager component. To activate add the following entry:

<persistence:entity-manager-factory
 auto-create="true" 
 name="oc4jEntityManagerFactory"
 persistence-unit-name="oc4j_example" />

We then need to tell Seam to use it, so we alter the managed-persistence-context injecting the Entity Manager Factory into the existing element:

<persistence:managed-persistence-context
 name="entityManager"
 auto-create="true"
 entity-manager-factory="#{oc4jEntityManagerFactory}" />
                           

This is a file that you must create so that RichFaces and Ajax4Jsf stylesheets will work with OC4J. This file basically tells OC4J not force its own inherited URL settings.

<?xml version = '1.0' encoding = 'utf-8'?>
<orion-application
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/
                                                            orion-application-10_0.xsd"
        schema-major-version="10"
        schema-minor-version="0"
        component-classification="internal">

    <imported-shared-libraries>
       <remove-inherited name="oracle.xml"/>
    </imported-shared-libraries>
</orion-application>

Now you need to tell the build.xml file that it needs to copy this file to the ear archive. Find the <target name="ear" description="Build the EAR"> target and modify the <copy todir="${ear.dir}/META-INF"> section to look like the following:

<copy todir="${ear.dir}/META-INF">
    <fileset dir="${basedir}/resources/META-INF">
       <include name="application.xml" />
       <include name="orion-application.xml"/>
       <include name="jboss-app.xml" />
    </fileset>
 </copy>