cipient,
and have received this message in error, please immediately return this
by email and then delete it.
> -Original Message-
> From: Matthieu Riou [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 30, 2007 9:05 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: Deploym
Hi guys,
One of our users in ODE is trying to deploy on JBoss. There seems to be some
configuration problems, most probably related to the presence of Hibernate
in the server. He's having the following stacktrace (I trimmed the non
relevant bits):
13:15:29,343 INFO [STDOUT] ERROR - ODEServer.in
e of a clue as to
why it failed.
On Apr 9, 2007, at 2:57 PM, Matthieu Riou wrote:
> I thought I had OpenJPA correctly placed but actually it wasn't
> copied at
> the right place. Thanks for the hint!
>
> Matthieu
>
> On 4/9/07, Marc Prud'hommeaux <[EMAIL PROTECTED]&
end us the setting of your classpath?
If you write a main() method that just tries "new
org.apache.openjpa.persistence.PersistenceProviderImpl()", what happens?
On Apr 9, 2007, at 12:25 PM, Matthieu Riou wrote:
> The System.out gives me the correct path to the URL:
>
> file:/home/dus
nce.xml? If you write a little main()
method that just does: System.out.println(getClass().getResource("/
META-INF/persistence.xml"), what does it show?
On Apr 9, 2007, at 11:54 AM, Matthieu Riou wrote:
> Hi,
>
> I'm having some difficulties testing a module that uses p
Hi,
I'm having some difficulties testing a module that uses persistent classes.
In that case the classes aren't loaded from a jar but are directly in the
classpath and so does the persistence.xml. However I always get "No
Persistence provider for EntityManager named ode-store". I've tried severa
er than later.
Thoughts anyone?
On Mar 26, 2007, at 11:54 AM, Matthieu Riou wrote:
> Hi guys,
>
> We've started preparing an incubator release for ODE and we're now
> using
> OpenJPA (pretty happily I should say). We can't use 0.9.6 as we need a
> couple of fi
Hi guys,
We've started preparing an incubator release for ODE and we're now using
OpenJPA (pretty happily I should say). We can't use 0.9.6 as we need a
couple of fixes from 0.9.7 so we've been using the snapshot so far. But as
you know we won't be able to release with it (and generally speaking
mostly of SQL Server 2000 here).
Cheers,
Matthieu
On 3/12/07, Hans J. Prueller <[EMAIL PROTECTED]> wrote:
Any special reason why you have been migrating from Hibernate to OpenJPA
(in addition to that it is an Apache project)?
regards,
hans
> -Ursprüngliche Nachricht-
> V
Hi guys,
Just a quick note to let you know we've completed the migration of Apache
ODE from Hibernate to OpenJPA. Everything seem to work pretty well now. I
expect a few glitches here and there as we run in heavily parallelized
environments but the transition has been pretty smooth.
Thanks a lot
Session
Beans.
Craig
On Mar 5, 2007, at 9:28 AM, Matthieu Riou wrote:
>> Hmm. I believe that you actually fall into the first category --
>> OpenJPA
>> only uses the ManagedRuntime when it thinks that it's integrating
>> with
>> JTA. It sounds like you're
eceived this message in error, please immediately return this
by email and then delete it.
> -Original Message-
> From: Matthieu Riou [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 05, 2007 8:48 AM
> To: Patrick Linskey
> Cc: open-jpa-dev@incubator.apache.org
> Subject:
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: Matthieu Riou [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 02, 2007 8:32 AM
> To: open-jpa-dev@incubator.apache.
Hi,
For ODE we're managing our transactions ourselves. We start them and commit
them explicitly. By the same token we create the EntityManagerFactory
ourselves. Is there a possibility to use the EntityManager injection in the
persistent classes in this context or do we have to implement our own
T
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: Matthieu Riou [mailto:[EMAIL PROTECTED]
> Sent: Wednesday,
t may be confidential, proprietary, copyrighted and/or
legally 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 delet
.merge(ret);
as ret is detached instance rather than new.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Matthieu Riou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 28, 2007 6:29 PM
To: open-jpa-dev@incubator.apache.org
Subject: OpenJPA & Transaction configura
Hi,
I'm going back at the OpenJPA implementation for the Apache ODE project and
am still having problems with the setup. Whan I try to persist a new object
I get an exception "Attempt to persist detached object". I guess the when I
instantiate my object OpenJPA can't locate its transactional cont
called. Alternately, you can put in some debugging code in
AbstractBrokerFactory.syncWithManagedTransaction() and rebuilding
OpenJPA and seeing if that is ever called, although that might be
more work.
On Jan 24, 2007, at 2:49 PM, Matthieu Riou wrote:
> Any idea why my transaction manager setting
Any idea why my transaction manager setting seems to be ignored?
Thanks,
Matthieu
On 1/16/07, Matthieu Riou <[EMAIL PROTECTED]> wrote:
Hi,
I've tried several thing:
- First I made sure that the tx was started when I get the EntityManager.
- Second I've tried calling em
tory?
>
> Finally, what happens if you call em.joinTransaction() and then
> commit the global transaction. Any change?
>
>
>
> On Jan 15, 2007, at 3:41 PM, Matthieu Riou wrote:
>
> >> Does your TxMgrProvider provide a correctly functioning
> >> Transactio
D, t0.NUMBER_OF_INSTANCES, t0.PROCESS_KEY,
t0.PROCESS_TYPE FROM ODE_PROCESS t0
58209 ode-dao TRACE [Thread-4] openjpa.jdbc.SQL - [0 ms] spent
58209 ode-dao TRACE [Thread-4] openjpa.jdbc.JDBC - [0 ms] close
Thanks,
Matthieu
On Jan 15, 2007, at 10:35 AM, Matthieu Riou wrote:
> Hi,
>
>
Hi,
I now have a working setup (at least something that starts) using a
programmaticaly provided datasource and transaction manager. Here is the
code now:
HashMap propMap = new HashMap();
propMap.put("openjpa.jdbc.DBDictionary", "
org.apache.openjpa.jdbc.sql.DerbyDictionary");
I see. I specifically had problems with relation tables though. I had
columns generated as _attribute_OTHERTABLENAME and the first _ didn't make
it through Derby. Hence the necessary usage of @ElementJoinColumn.
Are these mandated by the spec as well?
On 1/15/07, Abe White <[EMAIL PROTECTED]> wr
Hi,
We're using _attributes notations for instance attributes in Ode and I've
found slight problems with it in OpenJPA. If you use this notation the
default column names chosen by OpenJPA will start with _ which forces you to
use @Column and @ElementJoinColumn (unfortunately OpenJPA specific) all
happens.
If there is an error, be sure to post the complete stack trace.
On Jan 9, 2007, at 9:11 AM, Matthieu Riou wrote:
> If I don't set "openjpa.ConnectionDriverName" (and even if I set "
> openjpa.ConnectionFactory" with my datasource instance) I get the
> "
and more confused
as to which properties I should set...
On 1/8/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote:
Matthieu-
I think you want "openjpa.ConnectionFactory", not
"openjpa.ConnectionDriverName".
On Jan 8, 2007, at 9:45 AM, Matthieu Riou wrote:
&g
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
StringValue. Should I use another property instead?
My code:
propMap.put("openjpa.jdbc.DBDictionary", "
org.apache.openjpa.jdbc.sql.DerbyDictio
Sorry about that, I've been persistently reading your sentence the other way
around: use createEntityManager instead of createEntityManagerFactory. I've
finally got it in the right order, I guess I should get my eyes checked or
something. Thanks for insisting though :)
Now that I got it the right
I'm still having the same problem (it can't find my ConnectionDriverName
property). Now my code looks like:
HashMap propMap = new HashMap();
propMap.put("openjpa.jdbc.DBDictionary", "
org.apache.openjpa.jdbc.sql.DerbyDictionary");
propMap.put("openjpa.ManagedRuntime", TxMgrPr
Cool! I've tried to set openjpa.Log but like all other properties it doesn't
get considered by the entity manager. It's just like my whole Map gets
ignored. I'm also setting the DBDictionary but it also gets ignored as I get
the dictionary auto-detection message...
Something else I can do to debu
ateEntityManagerFactory
("ode-dao");
EntityManager em = emf.createEntityManager(propMap);
Where are the properties set on JDBConfigurationImpl? So I can check what
gets wrong in my case.
Thanks,
Matthieu
On 1/3/07, Matthieu Riou <[EMAIL PROTECTED]> wrote:
My ultimate goal is to provide di
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, at 5:01 PM, Mat
Right. Sorry about that. Even though my ConnectionDriverName is still not
properly picked up:
ERROR - ApplicationContext.log(675) | StandardWrapper.Throwable
<4|true|0.9.6-incubating-SNAPSHOT>
org.apache.openjpa.persistence.ArgumentException: A JDBC Driver or
DataSource class name must be specifi
But if I don't provide openjpa.ConnectionDriverName the call to
createEntityManager fails with an exception saying that ConnectionDriverName
should be provided (coming from DataSourceFactory):
<4|true|0.9.6-incubating-SNAPSHOT>
org.apache.openjpa.persistence.ArgumentException: A JDBC Driver or
Da
Sorry I've jumped too quickly to conclusions. The mistake was mine.
However I'm trying to initialize OpenJPA programmatically using the
following code:
HashMap propMap = new HashMap();
propMap.put("openjpa.ManagedRuntime", new TxMgrProvider(_txMgr));
propMap.put("openjpa.Con
Hi all,
I've been fighting for some time now with my OpenJPA configuration and just
discovered why. It seems that you *either* consider the persistence.xml file
*or* the map passed as parameter of Persistence.createEntityManagerFactory.
If you look at PersistenceProductDerivation.load(String rsrc
-Original Message-
> From: Matthieu Riou [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 13, 2006 5:07 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: Setting a datasource and a transaction manager
>
> But I can't use that. In the same way that I have to p
n the
"openjpa.ConnectionDriverName" property. This too is discussed at
http://incubator.apache.org/openjpa/docs/latest/manual/
manual.html#ref_guide_dbsetup
On Dec 13, 2006, at 4:42 PM, Matthieu Riou wrote:
> Sorry to be a pain but the thing is, we don't want to use any JN
ual/
manual.html#ref_guide_dbsetup
On Dec 13, 2006, at 4:21 PM, Matthieu Riou wrote:
> Thanks Marc! And what about the datasource? Is there another
> equivalent
> interface and property to use?
>
> On 12/13/06, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote:
>>
>> M
-kernel/src/main/java/org/
apache/openjpa/ee/AutomaticManagedRuntime.java?
view=markup&pathrev=468504 ).
See also: http://incubator.apache.org/openjpa/docs/latest/manual/
manual.html#ref_guide_enterprise_trans
On Dec 13, 2006, at 1:13 PM, Matthieu Riou wrote:
> Hi JPA guys,
>
>
Hi JPA guys,
In the Apache Ode podling we're currently working on replacing Hibernate
with OpenJPA. It's been working great so far but I have a couple of
questions. I'd need to set the transaction manager and the datasource
manually using the OpenJPA API and I've been unable to find the right cla
42 matches
Mail list logo
