If Kodo 4.1 is used with 3.4 developed applications, it does not allow
queries on interfaces any more essentially making it impossible to
transition 3.4 application without full conversion to JDO2.
I wonder if it is not possible to emulate JDO2 persistent interfaces
behavior from introspecting
Patrick,
As far as kodo.jdo.ProxyMap I fixed it (I had some custom proxies which
implement it)
My point was that you at least should log an exception if you hide it or
it is virtually impossible to figure out why the class could not be
loaded. Or better yet differentiate handle only ClassNotFound
Hi Patrick,
It is happening with Kodo 4.1
May be I have not converted some properties in config file?
-Original Message-
From: Patrick Linskey [mailto:[EMAIL PROTECTED]
Sent: Friday, October 13, 2006 8:08 PM
To: open-jpa-dev@incubator.apache.org
Subject: RE: DBDictionary bug? OracleDict
It sounds like you didn't recompile your sources between Kodo 4.0 and
Kodo 4.1. Kodo 4.0 used different package names than Kodo 4.1, and our
backwards compatibility efforts didn't include binary-compatibility.
(Sorry about the Kodo spam, btw.)
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
Well, if you're using Kodo, then this definitely should work. Is this
happening with a Kodo install, or a pure-OpenJPA install? If so, what
version of Kodo? (Presumably 4.1.)
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
N
All-
I would like to upload the OpenJPA docs and javadocs for the 0.9.0-
incubating to a more official location than the information place
where they currently result (http://people.apache.org/~mprudhom/
openjpa/site/openjpa-project/manual/index.html).
Does anyone have any recommendations f
In classForName()
You can find plenty of statements like this
try {
if (fullName || noPackage)
return Strings.toClass(name, resolve, loader);
return Strings.toClass(pkg + "." + name, resolve, loader);
} catch (RuntimeException re)
On Oct 13, 2006, at 1:14 PM, Roytman, Alex wrote:
Thank you very much Mark!
What version of Serp is bundled with Kodo? I need to get sources
because
the error I am seeing is in serp's String.toClass()
Serp version 1.11.0
Alex
-Original Message-
From: Marc Prud'hommeaux [mailt
Thank you very much Mark!
What version of Serp is bundled with Kodo? I need to get sources because
the error I am seeing is in serp's String.toClass()
Alex
-Original Message-
From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On Behalf Of
Marc Prud'hommeaux
Sent: Friday, October 13, 2006
Alex-
Kodo 4.1 is based on the "openjpa-0.9.0-incubating" release. You can
download the source from:
http://cwiki.apache.org/openjpa/downloads.html
Also, running "java kodo.conf.KodoVersion" will output the exact
OpenJPA version and the svn revision number that it was based on.
On Oc
Hello,
Is there any reason openjpa sources are not included with Kodo 4.1?
Since we do not know which SVN version is included with Kodo we can not
get it from SVN either. If we had it, it would help analyzing problems
and reporting issues properly.
For example while trying to run 3.x Kodo a
Yes it looks like documentation bug. I am using Kodo JDO and
\docs\full\html\ref_guide_professional_batch.html still have:
JDO properties format:
kodo.jdbc.DBDictionary: BatchLimit=25
while \docs\full\html\ref_guide_professional_batch.html
have updated info:
kodo.jdbc.SQLFactory: BatchLimit=1
Docs bug, actually. OpenJPA doesn't do batching.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries
Documentation still mentions BatchLimit for configuring batching but
using it causes
OpenJPA doesn't batch. The Kodo docs explain how to configure
batching in Kodo (see the docs on migrating to 4.1).
___
Notice: This ema
Documentation still mentions BatchLimit for configuring batching but
using it causes
Caused by: org.apache.openjpa.lib.util.ParseException: There was an
error while setting up the configuration plugin option "DBDictionary".
The plugin was of type "class
org.apache.openjpa.jdbc.sql.OracleDictionary
Thanks for sending the Channel base class. The problem is actually
very simple, and is explained here:
http://edocs.bea.com/kodo/docs41/full/html/
ejb3_overview_mapping_discrim.html
See the note about discriminator columns. The bottom line is that
when you use single-table inheritance ma
FYI, it seems that the changes that Abe did for OPENJPA-13 (via 453016)
resolved this problem. The various class types (Long, Integer, etc) are now
processed correctly. Thanks, Abe, for the solution.
Kevin
On 9/20/06, Kevin Sutter <[EMAIL PROTECTED]> wrote:
Hi,
It seems that if I map an ID
> Is it necessary to enhance all the classes at startup or could some classes
> be enhanced only when they are first required ?
a) Kodo will enhance all persistent classes listed in tag of
META-INF/persistence.xml or
b) setting "java -javagaent: myJPAApp" will enhance
classes before they ar
18 matches
Mail list logo