That's a pretty weird error ... it looks more like Maven isn't
installed correctly. Are you able to build any other projects using
maven?
If you re-install maven and delete (or move aside) your ~/.m2/
directory, do you still get the error?
On Mar 28, 2007, at 12:24 AM, Xibin Zeng
[
https://issues.apache.org/jira/browse/OPENJPA-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484775
]
Marc Prud'hommeaux commented on OPENJPA-189:
If you just execute the subquery by itself, does it return
[
https://issues.apache.org/jira/browse/OPENJPA-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux resolved OPENJPA-186.
Resolution: Invalid
This is almost certainly a general maven setup problem. Try
[
https://issues.apache.org/jira/browse/OPENJPA-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484917
]
Marc Prud'hommeaux commented on OPENJPA-186:
I haven't had any problems with surefire 2.3, but I don't
[
https://issues.apache.org/jira/browse/OPENJPA-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux resolved OPENJPA-186.
Resolution: Fixed
Fix Version/s: 0.9.7
Assignee: Marc
SurefireBooter.
The solution was to run mvn package -Dtest=false target few (3, in
this case) times.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On Behalf
Of Marc Prud'hommeaux
Sent: Wednesday, March 28, 2007 3:47 AM
To: open-jpa-dev
I've noticed that as well ... making a change to an included page
doesn't seem to trigger a re-export of all the static html pages that
include the changed page.
If you are a Confluence administrator (a privilege that was kindly
bestowed on me by David Blevins), you can manually
Phill-
I'm a little confused. Is this an error from OpenJPA or TopLink? Can
you post the entire stack trace of the error you are seeing?
On Mar 25, 2007, at 10:03 AM, Phill Moran wrote:
I have been struggling with an exception when running my JUnit 4.2
tests. It
complains about not
)
... 51 more
/code
-Original Message-
From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On
Behalf Of Marc
Prud'hommeaux
Sent: March 25, 2007 1:18 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: OPEN-JPA and Toplink 2.0.XX
Phill-
I'm a little confused. Is this an error from
. März 2007 23:46
An: open-jpa-dev@incubator.apache.org
Betreff: Re: AW: Forgot subject: Strange Could not locate metadata
for the
classError?
Marc Prud'hommeaux wrote:
Hans-
I don't see how the error could be data-related.
One thing: if you are using the same EMF from multiple threads,
do you
[
https://issues.apache.org/jira/browse/OPENJPA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux resolved OPENJPA-176.
Resolution: Fixed
Fix Version/s: 0.9.7
Implemented patch.
Exception
Hans-
There are only two possible conditions in which I can see this
problem happening:
1. the class com.lbslogics.ims.model.PositionLog is not loadable in
the current environment's classloader.
2. the PositionLog class was registered with the MetaDataRepository
during the lookup
. like that. The strange thing is
that it
worked several invocations before and after .. could it be a data-
related
problem? Anyway, I was not able to reproduce the error
Hans
-Ursprüngliche Nachricht-
Von: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] Im
Auftrag von
Marc
[
https://issues.apache.org/jira/browse/OPENJPA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux updated OPENJPA-176:
---
Attachment: OPENJPA-176.patch
The attached patch will change the prefix to look
[
https://issues.apache.org/jira/browse/OPENJPA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux reassigned OPENJPA-176:
--
Assignee: Marc Prud'hommeaux
Exception prefixes should be human-readable
[
https://issues.apache.org/jira/browse/OPENJPA-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux reassigned OPENJPA-89:
-
Assignee: Marc Prud'hommeaux
Bulk delete fails to delete owned many-to-many
[
https://issues.apache.org/jira/browse/OPENJPA-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux reassigned OPENJPA-135:
--
Assignee: Marc Prud'hommeaux
join fetch not returning duplicate references
,
-marina
Marc Prud'hommeaux wrote:
Marina-
On Mar 15, 2007, at 5:01 PM, Marina Vatkina wrote:
Hi,
I am part of the GlassFish persistence team and was wondering
how does OpenJPA support JPA auto DDL generation (we call it
java2db) in a Java EE application server.
Our application server
and not listing them. I'd be
interested to know if it works without.
On Mar 20, 2007, at 4:19 PM, Marina Vatkina wrote:
Marc,
Marc Prud'hommeaux wrote:
Marina-
On Mar 20, 2007, at 4:02 PM, Marina Vatkina wrote:
Marc,
Thanks for the pointers. Can you please answer the following set
Affects Versions: 0.9.6, 0.9.0
Reporter: Marc Prud'hommeaux
Priority: Trivial
OpenJPA prefixes all exception messages with a string of the form exception
type|is fatal|version, restulting in strings like 4|false|0.9.6-incubating
probably just
wind up having to perform the operation in-memory, which is usually
slower). Unfortunately, we'll probably also throw an exception when
you try to actually execute a subselect against the database.
On Mar 17, 2007, at 6:19 AM, Dave wrote:
On 3/16/07, Marc Prud'hommeaux
Marina-
On Mar 15, 2007, at 5:01 PM, Marina Vatkina wrote:
Hi,
I am part of the GlassFish persistence team and was wondering how
does OpenJPA support JPA auto DDL generation (we call it java2db)
in a Java EE application server.
Our application server supports java2db via creating two
Jeff-
OpenJPA provides the ability to generate a schema to an intermediate
XML file, but it doesn't require it. You can also create the schema
directly against the database.
Using the intermediate XML file can be useful if you want to generate
the schema, but then make additional
Kevin-
@XSecondaryTable has some attributes that @SecondaryTable doesn't have:
Index[] indexes() default {};
ForeignKey[] foreignKeys() default {};
However, it doesn't look like we actually support using it yet, as
per the following comment in AnnotationPersistenceMappingParser.java:
at the
code block for the case statement. Stupid me. I just assumed
there was
real code behind it... :-)
Have a good evening,
Kevin
On 3/15/07, Marc Prud'hommeaux [EMAIL PROTECTED] wrote:
Kevin-
@XSecondaryTable has some attributes that @SecondaryTable doesn't
have:
Index[] indexes
Hans-
My first guess is that Toplink might be eagerly loading the relation,
and OpenJPA is lazily loading it (i.e., it doesn't load the relation
when you issue the query, so every time you call person.getAccount(),
OpenJPA has to go back to the database). To verify this, you could
enable
I am fairly certain that the only way OpenJPA will ever think that a
native (i.e., SQL) query is not a select query is if it doesn't start
with select.
Is it possible that you didn't recompile the class after
experimenting with the quoteForUpdate @NamedNativeQuery? At some
point in the
Roger-
The query looks valid: it sounds like a pretty clear-cut bug. Can you
file a JIRA?
As for a workaround, is there an inverse from MailingList.subscribers
(e.g., Email.mailingList)? If so, then you might be able to re-cast
the query as:
UPDATE Email e SET e.totalDeliveries =
that I am not privy to.
Any help would be greatly appreciated as I believe this is a gating
factor for us moving forward testing the SPEC benchmarks as well as
DayTrader being developed for Apache.
John
On 3/13/07, Marc Prud'hommeaux [EMAIL PROTECTED] wrote:
I am fairly certain that the only way
Craig-
Yes, there do appear to be problems. If I clobber my repository (so
that the latest surefire plugin is downloaded) and try to run the
tests, everything fails with java.lang.ClassNotFoundException:
org.apache.openjpa.util.CacheMap.
I'll try to look into it tonight...
On Mar 13,
there...
Craig
On Mar 13, 2007, at 6:56 PM, Marc Prud'hommeaux wrote:
Craig-
Yes, there do appear to be problems. If I clobber my repository (so
that the latest surefire plugin is downloaded) and try to run the
tests, everything fails with java.lang.ClassNotFoundException
Components: kernel
Affects Versions: 0.9.6, 0.9.0
Reporter: Marc Prud'hommeaux
Priority: Minor
Currently, when setRollbackOnly is invoked on a Broker or EntityManager, there
is no way to specify the cause or reason for the invocation. Given that we
invoke
[
https://issues.apache.org/jira/browse/OPENJPA-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux updated OPENJPA-166:
---
Attachment: OPENJPA-166.patch
Attached is a patch that adds a Throwable argument
[
https://issues.apache.org/jira/browse/OPENJPA-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux resolved OPENJPA-166.
Resolution: Fixed
Fix Version/s: 0.9.7
Assignee: Marc
PM, Marc Prud'hommeaux wrote:
Patrick-
FYI, I had also put some of that sort of logic in the
org.apache.openjpa.persistence.test.SingleEMTest base test case.
We might want to consider merging duplicate functionality at some
point.
On Mar 6, 2007, at 6:09 PM, Patrick Linskey wrote:
Hi
Patrick-
FYI, I had also put some of that sort of logic in the
org.apache.openjpa.persistence.test.SingleEMTest base test case.
We might want to consider merging duplicate functionality at some point.
On Mar 6, 2007, at 6:09 PM, Patrick Linskey wrote:
Hi,
In implementing a new test
Dan-
Once you commit the transaction, is the PK assigned? Can you enable
SQL logging any show us the SQL that is executed in the transaction?
Finally, if you look up the Entity using a new EntityManager, is the
PK set correctly?
On Mar 2, 2007, at 3:38 PM, Dan Bush wrote:
I am using
We should be ignoring the whitespace. What is the error message?
On Mar 2, 2007, at 6:00 PM, Craig L Russell wrote:
Hey,
The Roller project found that OpenJPA didn't like line endings
(white space) in JPAQL queries in metadata. This is a surprise.
Don't we ignore white space in queries
[
https://issues.apache.org/jira/browse/OPENJPA-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux resolved OPENJPA-23.
---
Resolution: Fixed
Assignee: Marc Prud'hommeaux
I am fairly certain
[
https://issues.apache.org/jira/browse/OPENJPA-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476856
]
Marc Prud'hommeaux commented on OPENJPA-20:
---
Or, alternately, a bug in the documentation. The current
to Continuum.
Are there any continuum admins out there who can add this module?
David Blevins helped set this up last time, but I figured I'd ask
generally on the list, so as not to harass him directly.
If anyone knows of a better forum for this request, please do let me
know.
--
Marc
All-
Sorry for the long delay in looking into this (I was on vacation). I
can't imagine that this is anything but a bug in Derby, since it is
an NPE coming from Derby code (and it is a seemingly valid SQL
statement that intermittently works). However, I can't get it to
happen (on OS X).
How about just assigning cl = ClassLoader.getSystemClassLoader()
(which will hopefully never be null) when cl is null?
On Feb 27, 2007, at 7:29 AM, Patrick Linskey wrote:
Hi,
I was just looking at ObjectValue, and noticed something odd in the
code
snippet below. It looks like if cl is
: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On
Behalf Of Marc Prud'hommeaux
Sent: Monday, February 26, 2007 3:19 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: Test failure @ svn revision 511041
All-
Sorry for the long delay in looking into this (I was on vacation). I
can't imagine
[
https://issues.apache.org/jira/browse/OPENJPA-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475713
]
Marc Prud'hommeaux commented on OPENJPA-158:
+1. I've thought for a while that metadata parsing should
Dain-
I've reproduced this problem and reported it at:
https://issues.apache.org/jira/browse/OPENJPA-142
The only workaround is to add the @Entity(name=someAlias)
annotation to the class in addition to specifying it in the orm.xml
file.
On Feb 12, 2007, at 11:49 AM, Dain Sundstrom
[
https://issues.apache.org/jira/browse/OPENJPA-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472557
]
Marc Prud'hommeaux commented on OPENJPA-142:
This can be worked around by adding the annotation
9, 2007, at 6:09 AM, Geir Magnusson Jr. wrote:
+1
On Feb 9, 2007, at 12:41 AM, Marc Prud'hommeaux wrote:
It turns out that the JPA API we've been building against (the one
from https://maven-repository.dev.java.net/repository/
javax.persistence/jars/persistence-api-1.0.jar) is not actually
I agree that Nabble is much more navigable. I've been linking to the
mail-archives.apache.org archive just because all the examples I've
seen of posting vote results seem to reference that site.
On Feb 13, 2007, at 7:48 AM, Bryan Noll wrote:
I just wanted to throw this up here real
is final).
On Feb 12, 2007, at 4:33 AM, Kevin Sutter wrote:
Marc (and others),
Shouldn't OpenJPA be detecting these final classes and issuing an
error
message?
Kevin
On 2/12/07, Marc Prud'hommeaux [EMAIL PROTECTED] wrote:
Craig-
You're right that the classes shouldn't be final, but I don't
Dain-
I've been working on the TCK certification for OpenJPA. The terms of
Sun's TCK license dictate that I can't discuss the details with any
people who haven't signed Apache's NDA (see http://www.apache.org/
jcp/), but I can say that we might be able to make an announcement
regarding
Dain-
I just did a quick test with a mapped-superclass using an orm.xml
descriptor with all attributes defined in the superclass, and it
worked fine for me.
Are you using dynamic runtime enhancement, or build-time enhancement?
Can you enable TRACE-level logging (by setting the
Components: jpa
Reporter: Marc Prud'hommeaux
The XMLPersistenceMetaDataParser ignores the name attriburte of an entity
element, and instead always uses the default alias. For example, with the
following declaration in the orm.xml file:
entity name=Foo class=mypackage.Bar
the entity
)
at java.beans.XMLDecoder.readObject(XMLDecoder.java:220)
at
org.apache.openjpa.persistence.models.company.CompanyModelTest.checkM
odel(
CompanyModelTest.java:191)
... 22 more
On 2/10/07, Marc Prud'hommeaux [EMAIL PROTECTED] wrote:
Kevin-
Weird. From the error message, it looks like there is some problem
Oops! How odd that maven didn't given an error in the compile or
build stages.
Anyway, I've moved all the files to a company/ subdirectory. Please
let me know if you still have problems after updating.
Sorry about that.
On Feb 9, 2007, at 10:46 AM, Craig L Russell wrote:
Hi Mike,
Craig-
It would be really good to include the JIRA number in the commit
message text. That way, JIRA automatically will track the svn
checkin with the JIRA issue.
Yeah, you're right ... I fixed it after reading the first e-mail
about the problem, but before I noticed that a JIRA had
On Feb 3, 2007, at 12:39 AM, Marc Prud'hommeaux wrote:
In the interest of keeping up with the latest-and-greatest, I
propose we upgrade our project dependency on the stand-alone Derby
database JDBC driver for our testing and distribution zip from
Derby 10.2.1.6 to the latest public version
]
UPDATE I3.TEST_DATATYPES SET TEST_LOOKUP_ID = ? WHERE
TEST_DATATYPES_ID = ? [params=(long) 66, (long) 475]
graycol.gif
Marc Prud'hommeaux [EMAIL PROTECTED]
Marc Prud'hommeaux [EMAIL PROTECTED]
Sent by: Marc Prud'hommeaux [EMAIL PROTECTED]
02/07/2007 02:56 PM
Please respond to
open-jpa-dev
sure that this is always done)
2. Make the foreign key constraint nullable (is the database supports
nullable constraints; this has the added benefit of usually being
faster at commit time)
On Feb 8, 2007, at 11:52 AM, Marc Prud'hommeaux wrote:
Jeff-
I don't think optional is being
It turns out that the JPA API we've been building against (the one
from https://maven-repository.dev.java.net/repository/
javax.persistence/jars/persistence-api-1.0.jar) is not actually the
final version of the spec: there are some minor (and binary-
compatible) changes (some annotations
Jeff-
Why is that order bad? Is it because it violates your foreign key
constraints, or some other reason?
If it is a foreign key issue, you need to tell OpenJPA to read
foreign keys from the schema in order to ensure that SQL ordering is
done correctly. You can do this by setting the
Craig-
I mentioned an article earlier that I thought gave a pretty good
introduction and comparison:
http://www-128.ibm.com/developerworks/java/library/j-cq08296/
There's also a slew of other comparison articles listed at:
http://testng.org/doc/misc.html
I was going to experiment with
of the
individual
or entity named in this message. If you are not the intended
recipient,
and have received this message in error, please immediately return
this
by email and then delete it.
-Original Message-
From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On
Behalf Of Marc
In the interest of keeping up with the latest-and-greatest, I propose
we upgrade our project dependency on the stand-alone Derby database
JDBC driver for our testing and distribution zip from Derby 10.2.1.6
to the latest public version 10.2.2.0. This won't affect any core
code or
of the
individual
or entity named in this message. If you are not the intended
recipient,
and have received this message in error, please immediately return
this
by email and then delete it.
-Original Message-
From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On
Behalf Of Marc
Here's a good article comparing TestNG with JUnit:
http://www-128.ibm.com/developerworks/java/library/j-cq08296/
IMO, the groups feature is nice, but isn't necessarily sufficient to
justify a lot of effort porting over tests (since we could always
just check a system property before
Right. openjpa.loglevel=WARN is just converted to -
Dopenjpa.Log=DefaultLevel=WARN.
It'd be nice if you could just specify the latter from the console,
but unfortunately surefire doesn't propagate system properties
through to the forked Surefire test runner, so we need to special-
case
+ taskdef name=kodoc
classname=org.apache.openjpa.ant.PCEnhancerTask/
Shouldn't that be openjpac? Or maybe just enhance?
On Feb 1, 2007, at 2:03 PM, [EMAIL PROTECTED] wrote:
Author: pcl
Date: Thu Feb 1 14:03:31 2007
New Revision: 502374
URL:
/resources/org/apache/openjpa/jdbc/ant/an
tlib.xml
openjpa-kernel/src/main/resources/org/apache/openjpa/ant/antlib.xml
:-) His past comes back to haunt him... :-) Nice catch, Marc.
On 2/1/07, Marc Prud'hommeaux [EMAIL PROTECTED] wrote:
+ taskdef name=kodoc
classname
William-
I don't know how you specify collation, but if it is expressible via
the column type name, you could always set the type-name of the
column in the schema file (e.g., setting the type-name to be VARCHAR
WITH ASCII COLLATION).
If it needs to be specific in the CREATE TABLE part,
try it. Perhaps we need improve SQLServerDictionary at a
point. :-)
Thanks a lot for your help.
CREATE TABLE MyTable
(PrimaryKey int PRIMARY KEY,
CharCol varchar(10) COLLATE French_CI_AS NOT NULL
)
GO
On 1/31/07, Marc Prud'hommeaux [EMAIL PROTECTED] wrote:
William-
I don't know
PM, Marc Prud'hommeaux wrote:
William-
I didn't know it was an option to have a SQL Server instance be
case-sensitive.
Anyway, you can just specify this behavior by setting the
following property:
openjpa.jdbc.DBDictionary: schemaCase=preserve
Let us know if the problem still occurs
Dain-
Odd ... you certainly should see the statements. Are you sure you
aren't running against a database where the tables already exist
(since OpenJPA won't try to create tables when they exist)?
Can you see any SQL statements in the logged messages at all (e.g.,
when you run a query)?
William-
I didn't know it was an option to have a SQL Server instance be case-
sensitive.
Anyway, you can just specify this behavior by setting the following
property:
openjpa.jdbc.DBDictionary: schemaCase=preserve
Let us know if the problem still occurs after you try this setting.
[
https://issues.apache.org/jira/browse/OPENJPA-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467623
]
Marc Prud'hommeaux commented on OPENJPA-5:
--
I feel that this issue is merely to make it possible for OpenJPA
privileged, and is intended solely for the use of the
individual
or entity named in this message. If you are not the intended
recipient,
and have received this message in error, please immediately
return this
by email and then delete it.
-Original Message-
From: Marc Prud'hommeaux
[
https://issues.apache.org/jira/browse/OPENJPA-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467214
]
Marc Prud'hommeaux commented on OPENJPA-108:
This sounds like a bug with the IBM JVM, as reported
[
https://issues.apache.org/jira/browse/OPENJPA-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467215
]
Marc Prud'hommeaux commented on OPENJPA-107:
This is the same comment as I made in OPENJPA-108
[
https://issues.apache.org/jira/browse/OPENJPA-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467216
]
Marc Prud'hommeaux commented on OPENJPA-110:
It looks like you are getting back a list of Integers
[
https://issues.apache.org/jira/browse/OPENJPA-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux resolved OPENJPA-111.
Resolution: Invalid
Section 3.6.3 of the JPA spec: Only positional parameter
these to make sure
they are
viable. On paper, they look like the solution. But, Craig's
concern about
allowing new member elements within existing elements is a valid
question.
Any volunteers?
Kevin
On 1/16/07, Marc Prud'hommeaux [EMAIL PROTECTED] wrote:
That indeed does sound like a better
Rahul-
If it worked, then the persistence tests should pass. E.g., the
following should work from the top-level of the project:
mvn clean test -Dtest=TestPersistence -Dopenjpa.loglevel=trace
On Jan 20, 2007, at 5:49 PM, Rahul Thakur wrote:
Hi,
I'd like to put together a couple of
- Original Message - From: Marc Prud'hommeaux
[EMAIL PROTECTED]
To: open-jpa-dev@incubator.apache.org
Sent: Tuesday, January 09, 2007 9:58 PM
Subject: Re: Missing ProductDerivation resource error
Rahul-
Did you misspell apache in
org.apacha.maven.continuum.model.project.Schedule?
On Jan
to the contribution. I can't really comment on the
likelihood of whether that will ever happen or not, but I agree that
it would be nice.
My two cents worth... :-)
Kevin
On 1/11/07, Marc Prud'hommeaux [EMAIL PROTECTED] wrote:
David-
Batching functionality was not included in the OpenJPA code
in this message. If you are not the intended
recipient,
and have received this message in error, please immediately return
this
by email and then delete it.
-Original Message-
From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On
Behalf Of Marc Prud'hommeaux
Sent: Monday, January 15, 2007
Matthieu-
Does your TxMgrProvider provide a correctly functioning
TransactionManager? OpenJPA will register a Synchronization with it,
which should get committed when your global transaction is committed.
Do you see any log messages at all when you commit the global
transaction?
On
OpenJPA people-
A limitation of the JPA specification is that there is no built-in
way to put implementation-specific extensions in an orm.xml file,
which limits the use of OpenJPA's many useful extensions to only
being expressible annotations. Past suggestions for getting around
this
Prud'hommeaux [mailto:[EMAIL PROTECTED] On
Behalf Of Marc Prud'hommeaux
Sent: Wednesday, January 10, 2007 3:23 PM
To: open-jpa-dev@incubator.apache.org
Subject: [VOTE] Have official OpenJPA site use the confluence
wiki page
I just noticed that the OpenEJB main page uses the confluence wiki
(http
Matthieu-
That's pretty weird. What happens if you just try to manually commit
the transaction from the EntityManager itself (with em.getTransaction
().commit())?
Also, has the global transaction already been started as the point
when you obtain the EntityManager from the
I think you also want to set openjpa.Optimistic to false. That
will default to non-optimistic transactions.
Setting the other properties (openjpa.LockManager,
openjpa.ReadLockLevel, openjpa.WriteLockLevel) are probably
unnecessary.
On Jan 12, 2007, at 11:56 AM, Ritika Maheshwari
On Jan 10, 2007, at 12:12 AM, wanyna wrote:
Hi all.
I have two questions:
1.
Here is my sql string:
select 'xxx', TABLE_A.column1 from TABLE_A;
there is a string 'xxx' as a constant value,
how to translate it to JPQL?
I don't think it is possible. Why would you need to do that?
2.
Another
[
https://issues.apache.org/jira/browse/OPENJPA-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463713
]
Marc Prud'hommeaux commented on OPENJPA-98:
---
I've never seen any problem like this. It is interesting
Rahul-
Did you misspell apache in
org.apacha.maven.continuum.model.project.Schedule?
On Jan 9, 2007, at 12:53 AM, Rahul Thakur wrote:
okies, my work is progressing in trickles as I am squeezing some
time outside work :-)
Here's the latest issue while trying to process a bunch of
Matthieu-
I think you want openjpa.ConnectionFactory, not
openjpa.ConnectionDriverName.
On Jan 8, 2007, at 9:45 AM, Matthieu Riou wrote:
Hi,
I've just tried your fix after compiling the OpenJPA trunk. I'm
getting a
ClassCastException as the openjpa.ConnectionDriverName is set as a
Vlad-
I didn't get any attachments in that last message (perhaps they were
stripped by the list server).
It might be interesting the see the java stack trace parts of the JVM
dump, in case that might shed light on the situation.
Also, what database are you using? It could be that the
PROTECTED]
Office (905) 413-3853
Marc Prud'hommeaux [EMAIL PROTECTED]
Sent by: Marc Prud'hommeaux [EMAIL PROTECTED]
08/01/2007 03:17 PM
Please respond to
open-jpa-dev@incubator.apache.org
To
open-jpa-dev@incubator.apache.org
cc
Subject
Re: Deadlock when insert in t1 and find in t2
Vlad-
I
Craig-
It sounds like we are initializing an int field, but we are reading
null from the database.
Can you check the database to see if there are any nulls in the
column to which the id field is being mapped?
Also, if you change the field type from int to Integer, do you
get the same
, 2007, at 3:09 PM, Marc Prud'hommeaux wrote:
Kevin-
Also, this exception is supposedly only being produced with
Oracle, not
DB2. (I have not been able to verify that yet.) This would
seem to
indicate that it's dictionary-specific, but I'm not seeing
anything there
yet...
Does Oracle
Dain-
Note that in many cases, we track the thread's context class loader,
but only use it as an auxiliary loader to check when searching for
classes: typically, class loading will go happen via the
Configuration's getClassResolverInstance().
That isn't to say that there aren't potential
Matthieu-
Can you send the complete stack trace?
Also, I don't think this is the cause of the problem, but why are you
specifying both ConnectionDriverName and ConnectionFactory? With
ConnectionFactory specified, you shouldn't need to specify the
ConnectionDriverName.
On Jan 3, 2007,
101 - 200 of 310 matches
Mail list logo
