hi,
as you know I am switching from EJB2.1 CMP to JPA (OpenJPA). I'd like to
know the preferred way to perform attribute initialisation
of newly created entity instances, e.g.
we initialized our EJB2.1 CMP entity beans with
ejbCreate(String cid, Integer someOtherValue)
{
setabc();
Am Donnerstag, den 12.04.2007, 08:57 -0700 schrieb Craig L Russell:
> The no-arg constructor can be private.
fine - is this an OpenJPA specific feature or part of the JPA spec? You
have to know: in our current EJB2.1 CMP EB implementation,
we - unconsciously - used a lot of not-spec-compliant s
+1
Am Montag, den 16.04.2007, 11:10 -0500 schrieb Michael Dick:
> OpenJPA People-
>
> In accordance with the Incubating Releases guidelines at
> http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
> , I've taken another shot at making a release and start a vote on publishing
Phill,
I am still getting the same warning - although I am using a
0.9.7-snapshot that is some weeks old meanwhile:
160 lbsims INFO [RMI TCP Connection(3)-127.0.1.1] openjpa.Runtime -
Starting OpenJPA 0.9.7-incubating-SNAPSHOT
363 lbsims INFO [RMI TCP Connection(3)-127.0.1.1] openjpa.jdbc
Jacek,
thank you for diving into this. I added the following node to my
persistence.xml right
after the - List:
true
It seems that the "duplicate query" warning stays - did I add it the
wrong way?
hans
Am Mittwoch, den 18.04.2007, 00:16 +0200 schrieb Jacek Laskowski:
> On 4/
Am Donnerstag, den 19.04.2007, 12:14 -0500 schrieb Jay D. McHugh:
> You could try that and see if it makes a difference (hopefully it
> will)
Unfortunately NOT.
Can anybody else with that duplicate-query problem try it?
Hans
signature.asc
Description: Dies ist ein digital signierter Nachrich
Jacek,
don't bother that you messed something up. At least from the XML-Schema
definition I was able to derive the right
things I think:
Am Donnerstag, den 19.04.2007, 20:36 +0200 schrieb Jacek Laskowski:
> Not applicable to Java SE
> persistence units.
So in that case this won't change anyth
Am Donnerstag, den 19.04.2007, 21:34 +0200 schrieb Jacek Laskowski:
> Did you configure it by purpose? These are settings I have never used
> so I doubt if I help much.
Definitely. I have to mix EJB2.1 CMP entity beans with the new JPA POJO
CMP3 Entity Beans within the J2EE1.4
application serv
+1
hans
Am Donnerstag, den 03.05.2007, 07:22 -0700 schrieb Craig L Russell:
> This vote is to send the attached draft board resolution to the
> incubator for the purpose of graduation from the incubator to the
> Apache OpenJPA project.
>
> +1 We're ready; let's graduate
>
> 0 Don't care
Hi there,
I'm trying to migrate our "old" J2EE1.4 / EJB2.1 applications persistence to
openJPA. Currently I got stuck when
trying to configure OpenJPA persistence, when creating the
EntityManagerFactory and the EntityManager instance,
I get the following error:
<4|true|0.9.6-incubating>
va:comp/
> UserTransaction)
>
> if that doesn't work, try:
>
> openjpa.ManagedRuntime: jndi(TransactionManagerName=/
> UserTransaction)
>
> (apparently, Jonas' UserTransaction implementation is also their
> TransactionManager implementation)
>
> If that doe
tems, Inc., its subsidiaries and affiliated
> entities, that 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 rece
As some of you may remember, I am using OpenJPA within an "old" Java2EE
1.4/EJB2.1 container to perform
a step-by-step or bean-by-bean migration from our EJB2.1 CMP entity beans to
new EJB3 Beans with JPA.
For the IDs of the Entity Beans we have been using a
Container-Generated-Value and I pla
-Ursprüngliche Nachricht-
Von: Hans J. Prueller [mailto:[EMAIL PROTECTED]
Gesendet: Samstag, 10. Februar 2007 18:24
An: open-jpa-dev@incubator.apache.org
Betreff: Using @GeneratedValue for IDs on already existing tables
As some of you may remember, I am using OpenJPA within an &quo
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 delete it.
>
> > -Original Messa
thanks for this link but this section only describes the different
algorithms that are provided to get the generated value - it does
not mention the case what happens if we try to save a new persistent
entity with a generated PK value that already exists in the DB?
I can remember a legacy persiste
aries and affiliated
> entities, that 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
to use a
> OpenJPA UUID without conflicts. If the vendor is using some sort of
> DB sequence, you should be able to start a new sequence for OpenJPA
> using a much larger starting number.
>
> -dain
>
> On Feb 13, 2007, at 9:00 AM, Hans J. Prueller wrote:
>
> > thanks
or IDs on already existing
> tables
>
>
> On Feb 13, 2007, at 10:06 AM, Hans J. Prueller wrote:
>
> >> Can you tell us your current J2EE vendor, and if possible the
> >> generation
> >> strategy selected in the vendor deployment descriptor. If not,
>
Hi there,
meanwhile I succeeded in getting OpenJPA to work within my J2EE 1.4
container and
I was able to replace a CMP entity bean by a JPA Pojo and perform basic
operations
on it (insert/persist, query).
The hi-lo table sequence generator works fine, so I can avoid conflicts with
exis
hi together,
I am evaluating JPA(OpenJPA) for one of our customers. The usage scenarios
have a very special
problem of which I do not know if there is a clear solution by using JPA:
The customers Oracle databases have very restricted access privileges:
==> the testing and developme
Kevin,
if you missed previous discussions on the list: I am using OpenJPA within
a Java2EE 1.4 container - therefore I cannot use container injection
unfortunately!
hans
> -Ursprüngliche Nachricht-
> Von: Kevin Sutter [mailto:[EMAIL PROTECTED]
> Gesendet: Mittwoch, 21. Februar 2007 12:58
Patrick,
I'm currently trying your tip with a PersistenceService util class doing
the lookup of a synchronized entity manager. The problem is that your sample
code does not work!
in fact the statement
final BrokerFactory bf = OpenJPAPersistence.cast(emf);
is the problem. the above "cast" does
, 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 delete it.
>
that 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
> Notice: This email message, together with any attachments, may contain
> information of BEA Systems, Inc., its subsidiaries and affiliated
> entities, that may be confidential, proprietary, copyrighted and/or
> legally
ial, 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 delete
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-
> Von: Matthieu Riou [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 13. März 2007 03:33
> An: open-jpa-dev@incubator.apache.or
Hi together,
please allow me a simple question: I am currently preparing a "JPA" workshop
for a customer to show the developers
the new way of working with JPA persistence in Java EE 5. Just to show one
of the advantages of an open standard like JPA
I prepared the example to switch between Op
I received a very strange error message from OpenJPA on a method that is
being called very often subsequently. The
most time it works, suddenly it failed with:
Could not locate metadata for the class using alias "PositionLog".
Registered alias mappings: "{PositionLog=[class
com.lbslogics.ims.mode
Weitergeleitete Nachricht
> Von: Hans J. Prueller <[EMAIL PROTECTED]>
> Antwort an: open-jpa-dev@incubator.apache.org
> An: open-jpa-dev@incubator.apache.org
> Betreff: No Subject
> Datum: Fri, 23 Mar 2007 13:12:26 +0100
>
>
> I received a v
full stack trace (up until application specific stuff) is:
2007-03-22 21:34:53,287 : SEVERE : WorkThread-2/34 : Logger.log :
system exception in business method:
<4|true|0.9.7-incubating-SNAPSHOT>
org.apache.openjpa.persistence.ArgumentException: Could not locate
metadata for the class using alias
as not yet been called for
> that EntityManager's EntityManagerFactory.
>
> If this is something you can reproduce, it would be interesting if we
> could see more logging output (enabled by setting the "kodo.Log"
> property to "DefaultLevel=TRACE"), especially tho
u expect users to always specify this setting when they
> >>> decide to deploy it to a multi-threaded container?
> >>>
> >>> thanks,
> >>> -marina
> >>>
> >>> Marc Prud'hommeaux wrote:
> >>>
> >>>&
Hi together,
I succeeded in integrating OpenJPA into our J2EE1.4 container, running
side-by-side within the same JTA transactions as
container managed EJB2.1 CMP entity beans.
The lookup/creation of the EntityManager instances is synchronizing with
the JTA TXs as you suggested some weeks ago
on t
nt).
any ideas?
Hans
Am Mittwoch, den 28.03.2007, 20:47 +0200 schrieb Hans J. Prueller:
> Hi together,
>
> I succeeded in integrating OpenJPA into our J2EE1.4 container, running
> side-by-side within the same JTA transactions as
> container managed EJB2.1 CMP entity beans.
&
The usage case of the EM is, that I call a
PersistenceService.getEntityManager() method in every method of my
SLSB's, the SLSBs all have
the "Required" attribute set for TXs, so every time I call the getEM()
method, there should be an already running JTA TX.
This is the code:
logger.log(Level.F
Am Mittwoch, den 28.03.2007, 12:43 -0700 schrieb Patrick Linskey:
> What happens if you set 'openjpa.TransactionMode' to 'managed' as
> well?
I will give it a try. Can you explicitly confirm that it shouldn't be a
multithreading problem where there are serveral entitymanagers
created in differen
Am Mittwoch, den 28.03.2007, 13:30 -0700 schrieb Patrick Linskey:
> Are you ever sharing EMs across multiple sequential JTA transactions?
As far as I can say: definitely NO. But the EMF used to create the EM's
is held as a static member of a Helper Class.
I.e. 2 different threads accessing the E
>> If you want to access a single EM from multiple
>> threads, you should set the openjpa.Multithreaded property
accordingly
As I mentioned, there is a static EMF in a helper class used to obtain
the EM's called from different
threads. does above property also resolve multithreaded access to the
E
Am Donnerstag, den 29.03.2007, 10:09 -0700 schrieb Patrick Linskey:
> If somehow you're holding onto a reference to the EM across multiple
> transactions, or the pool is somehow doling out duplicates or
> something,
> you should now see exceptions thrown indicating that the EM is closed.
> Alterna
ore details
> > about what the
> > > biz method in question is?
> > >
> > > (None of the messages you've posted look like anything that OpenJPA
> > > would ever generate.)
> > >
> > > -Patrick
> > >
> > > --
42 matches
Mail list logo
