On 9/12/07, Jason Lee <jason_at_steeplesoft.com> 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. :)
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=118515
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="
http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="
http://xmlns.oracle.com/oracleas/schema/orion-application-10_0.xsd"
deployment-version="10.1.3.1.0" default-data-source="jdbc/OracleDS"
component-classification="external"
schema-major-version="10" schema-minor-version="0" >
<web-module id="iota" path="iota.war" />
<persistence path="persistence" />
<imported-shared-libraries>
<remove-inherited name="oracle.toplink"/>
<remove-inherited name="oracle.xml"/>
<remove-inherited name="oracle.xml.security"/>
</imported-shared-libraries>
<principals path="principals.xml" />
<jazn provider="XML" />
<log>
<file path="application.log" />
</log>
</orion-application>
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
http://blogs.steeplesoft.com