Re: OC4J doesn't seem to like the RI

From: Jason Lee <>
Date: Wed, 12 Sep 2007 13:46:35 -0500

On 9/12/07, Jason Lee <> wrote:
> I *think* I can, on a per-app basis, tell oc4j not to use certain
> classes. I'm exploring that now. I can probably change the app server lib
> itself, but I don't think our admins will like that approach as we look at a
> production roll out. :)

OK. I got it working, but now Seam is having some trouble. :)

Turns out, I just need META-INF/orion-application.xml to tell oc4j to ignore
some container-provided classes:

<?xml version="1.0"?>

<orion-application xmlns:xsi=""
deployment-version="" default-data-source="jdbc/OracleDS"
  schema-major-version="10" schema-minor-version="0" >
    <web-module id="iota" path="iota.war" />
    <persistence path="persistence" />
        <remove-inherited name="oracle.toplink"/>
        <remove-inherited name="oracle.xml"/>
        <remove-inherited name=""/>
    <principals path="principals.xml" />
    <jazn provider="XML" />
        <file path="application.log" />

I copied that from the deployment directory, which oc4j created based on my
selections during the deployment process. :)

Jason Lee, SCJP
Software Architect -- Objectstream, Inc.
JSF RI Dev Team