Hi,
I'm getting an illegal SQL exception when working with OpenJPA
0.9.8-incubator-SNAPSHOT and PostgreSQL 8.2.3 with an persistent
attribute defined as follows:
@Column(precision = 7, scale = 3)
public BigDecimal getPensja() {
return pensja;
}
OpenJPA generates
pensja DOUBLE
On 4/19/07, Craig L Russell <[EMAIL PROTECTED]> wrote:
Post processing is a common term used to describe anything done to
a .class file after being generated by the compiler. And there
certainly is the notion of post processing class files in JPA.
I stand corrected. Great you spot it and corre
I’m having the same exception. Strange is that the IDENTICAL codebase runs
without errors under Toplink JPA. I’ve only changed the provider and
properties in the persistence.xml and included the OpenJPA jars to the
project. (That is what JPA should be able to do, afterall.)
--
View this message i
On 4/20/07, tbee <[EMAIL PROTECTED]> wrote:
I'm having the same exception. Strange is that the IDENTICAL codebase runs
without errors under Toplink JPA. I've only changed the provider and
properties in the persistence.xml and included the OpenJPA jars to the
project. (That is what JPA should be
tbee wrote:
>
>
>
> Jacek Laskowski-4 wrote:
>>
>> So I read it that you're relying "on the other mechanisms" TopLink JPA
>> provides.
>>
>
> Ah, no, all classes are defined in the persistence.xml. In fact I turned
> autodetection explicitely off when I was trying Hibernate (OpenJPA is
> a
Jacek Laskowski-4 wrote:
>
> I've never used @MappedSuperclass so I can't comment on it. Could you
> present your persistence.xml (and orm.xml if used)?
>
Sure!
http://java.sun.com/xml/ns/persistence";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schem
On 4/20/07, tbee <[EMAIL PROTECTED]> wrote:
http://java.sun.com/xml/ns/persistence";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd";
On 4/20/07, tbee <[EMAIL PROTECTED]> wrote:
Is it possible this has to do with the way I've setup the entity classes?
What I do is have an @Entity class without any fields and it extends a
@MappedSuperclass which is generated from the DB and where all the actual
fields are declared.
I've never
Jacek Laskowski-4 wrote:
>
> So I read it that you're relying "on the other mechanisms" TopLink JPA
> provides.
>
Ah, no, all classes are defined in the persistence.xml. In fact I turned
autodetection explicitely off when I was trying Hibernate (OpenJPA is
attempt 3); my persistent classes ar
The spec defines the following limitations of a MappedSuperclass:
2.1.9.2 Mapped Superclasses
...
A mapped superclass, unlike an entity, is not queryable and cannot be passed as
an argument to EntityManager or Query operations. A mapped superclass cannot be
the target of a persistent relationsh
Marina Vatkina wrote:
>
> The spec defines the following limitations of a MappedSuperclass:
>
> 2.1.9.2 Mapped Superclasses
> ...
> A mapped superclass, unlike an entity, is not queryable and cannot be
> passed as
> an argument to EntityManager or Query operations. A mapped superclass
> canno
I'll probably have to write an abstraction on top of JPA with a
different "driver" for each implementation (OpenJPA, TopLink) so I can
(a) deal with these issues and (b) use extensions without tying
application code to a particular vendor.
David
Patrick Linskey wrote:
Yeah, it's not ideal, a
Have you checked with Spring/JUnit they support rollback during tests
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of David Van Couvering
Sent: April 20, 2007 1:46 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: Help requested around rollback semanti
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
a "0.9.7-incubating" release of OpenJPA.
The release candidate is at:
http:
tbee wrote:
Marina Vatkina wrote:
The spec defines the following limitations of a MappedSuperclass:
2.1.9.2 Mapped Superclasses
...
A mapped superclass, unlike an entity, is not queryable and cannot be
passed as
an argument to EntityManager or Query operations. A mapped superclass
cannot be
> How can you define relationships in the mapped superclass that are
*specified*
> in terms of the entities?
Quite simple:
@Entity
class Article extends Article2
@MappedSuperclass
class Article2
@ManyToOne
private Manufacturer; // note: not Manufacturer2!!
> You can always change the ann
tbee wrote:
How can you define relationships in the mapped superclass that are
*specified*
in terms of the entities?
Quite simple:
@Entity
class Article extends Article2
@MappedSuperclass
class Article2
@ManyToOne
private Manufacturer; // note: not Manufacturer2!!
You can always
+1
On Apr 20, 2007, at 12:41 PM, Michael Dick wrote:
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
a "0.9.7-incub
+1
--
Patrick Linskey
BEA Systems, Inc.
___
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, pro
Marina Vatkina wrote:
>
> I didn't suggest to remove the existing @Entity annotation - what I
> suggested
> was to change the @MappedSuperclass to be an @Entity, *and* make it
> *abstract*.
> The latter will mean that you'll never get its instances back.
>
Ok, do you mean:
@Entity
class A
20 matches
Mail list logo
