4.1.4 - June 2007
Unenhanced classes are not loaded by JBoss when attempting to use Kodo runtime enhancement feature
Problem:
The JBoss classloader is unable to find unenhanced application classes
in an ear
file when attempting to run the
Kodo runtime enhancement feature.
Workaround: Use the build-time enhancement feature, that is, enhance the persistent entity classes before packaging/deploying them in the Enterprise/Web application.
Deploying kodo-jdo.rar
causes WebLogic Server 8.1
crash on Sun JDK 1.4
Problem: The Kodo JPA binding depends on JDK 5 language features and libraries. When running in a JDK 1.4 environment, Kodo automatically detects features that are dependent on JRE 5 and invalidates them. However, Weblogic Server 10.0 with Sun JDK 1.4 can cause a server crash when initializing Kodo.
Workaround:
Invoke Weblogic server with the Java System
option -Xverify:none
. You can change
your startWeblogic.cmd/sh
script to
include the -Xverify:none
option to invoke
weblogic.Server
.
Kodo cannot find package.jdo
in the
ear
file while integrated with Sun Application Server PE 8.2
Problem:
Kodo cannot find package.jdo
in the
ear
file while integrated with Sun Application Server PE 8.2.
Workaround:
Put package.jdo
into
${domain-dir}/lib/classes
, and restart the application server.
Query projection including a LOB
field and
using DISTINCT
in a nested SELECT
does not work.
Problem: Query has this known limitation when all of the following is true:
You are using nested SELECT
s (as specified by
kodo.jdbc.DBDictionary:SupportsSubselect=true
in your configuration)
A nested SELECT
is DISTINCT
The primary SELECT
selects a
LOB
field in its projection
DBDictionary: SupportsSubselect=false