tbee wrote:
Patrick Linskey wrote:
I think that if you do 1, 2, 3, 5, and 6, you should be in good shape.
This indeed seems to work!
BTW, Toplink just now also had its lazy loading issue solved: turns out
@MappedSuperclass classes must be listed in the persistence.xml.
@MappedSupercla
-dev@incubator.apache.org
> Subject: RE: Open JPA error-Could not locate metadata for the
> class using alias
>
>
>
>
> Patrick Linskey wrote:
> >
> > I think that if you do 1, 2, 3, 5, and 6, you should be in
> good shape.
> >
>
> This indeed
April 26, 2007 10:17 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: RE: Open JPA error-Could not locate metadata for the
> class using alias
>
>
>
>
> Patrick Linskey wrote:
> >
> > FYI, once I commit a fix to OPENJPA-229, you'll be able to use
e 3 open (1 it already has). So
the decision is still open. It appears that using a business model this way
is not something that is done often.
--
View this message in context:
http://www.nabble.com/Open-JPA-error-Could-not-locate-metadata-for-the-class-using-alias-tf3561516.html#a10204857
Sent
www.nabble.com/Open-JPA-error-Could-not-locate-metadata-for-the-class-using-alias-tf3561516.html#a10196445
Sent from the open-jpa-dev mailing list archive at Nabble.com.
please immediately return this
by email and then delete it.
> -Original Message-
> From: tbee [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 25, 2007 2:31 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: RE: Open JPA error-Could not locate metadata for the
> cl
//www.nabble.com/Open-JPA-error-Could-not-locate-metadata-for-the-class-using-alias-tf3561516.html#a10177260
Sent from the open-jpa-dev mailing list archive at Nabble.com.
this
by email and then delete it.
> -Original Message-
> From: tbee [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 25, 2007 1:06 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: RE: Open JPA error-Could not locate metadata for the
> class using alias
>
AM
> To: open-jpa-dev@incubator.apache.org
> Subject: RE: Open JPA error-Could not locate metadata for the
> class using alias
>
>
>
>
> Patrick Linskey wrote:
> >
> > Ok... the problem is that OpenJPA requires that you run the OpenJPA
> > cla
a" classes for tables with more
than one field in the PK and the corresponding @IdClass. Maybe the quick
change to "@Entity extends @Entity" has a bug, now that I think of it, the
@IdClass may refer to a PK class that actually is in the generated package.
Could you elaborate?
--
Vi
oup's perusal.
> >
>
> Alrighty then: OPENJPA-228
>
> This is the BM archive with "@Entity extends @Entity" instead
> of "@Entity extends @MappedSuperclass". But I do not believe
> OpenJPA gets to that part, because that actually does not
&g
To: open-jpa-dev@incubator.apache.org
> Subject: RE: Open JPA error-Could not locate metadata for the
> class using alias
>
>
>
>
> Patrick Linskey wrote:
> >
> > Could you try out the almost-final OpenJPA 0.9.7 bits instead? The
> > candidate (currentl
pa.persistence.QueryImpl.getResultList(QueryImpl.java:269)
at nl.reinders.bm.BMTestOpenJPA.main(BMTestOpenJPA.java:41)
How about there being two classes with the same shortname?
--
View this message in context:
http://www.nabble.com/Open-JPA-error-Could-not-locate-metadata-for-the-class-us
Tom,
I don't see nl/reinders/bm/generated/... classes listed in persistence.xml.
While the provider might find that a superclass is an entity, for a spec
compliant application, you must list all of them.
-marina
tbee wrote:
Patrick Linskey wrote:
I don't think that uploading to this mai
t actually does not make a difference.
--
View this message in context:
http://www.nabble.com/Open-JPA-error-Could-not-locate-metadata-for-the-class-using-alias-tf3561516.html#a10175457
Sent from the open-jpa-dev mailing list archive at Nabble.com.
t; "{Article=null}"
>
> What I'm wondering about: when running under Toplink there is
> an output "alias defaults to ". Is there something that
> Toplink assumes about this alias that actually should be
> configured and where OpenJPA has problems with?
>
uot; the example code? How to solve the missing Informix
database?
--
View this message in context:
http://www.nabble.com/Open-JPA-error-Could-not-locate-metadata-for-the-class-using-alias-tf3561516.html#a10175078
Sent from the open-jpa-dev mailing list archive at Nabble.com.
L PROTECTED]
> Sent: Tuesday, April 24, 2007 11:04 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: RE: Open JPA error-Could not locate metadata for the
> class using alias
>
>
>
>
> Patrick Linskey wrote:
> >
> > What's the OpenJPA version in
Patrick Linskey wrote:
>
> What's the OpenJPA version in question?
>
openjpa-project-0.9.6-incubating-binary
--
View this message in context:
http://www.nabble.com/Open-JPA-error-Could-not-locate-metadata-for-the-class-using-alias-tf3561516.html#a10174891
Sent from th
lass nl.reinders.bm.Relationcat] is
being defaulted to: Relationcat.
Toplink decides to default an alias. The OpenJPA error is something about
not being able to find a alias. What is it with this alias and do I need to
specify it somewhere?
--
View this message in context:
http://www.nabble.com/Open-J
Do you have an orm.xml (or another .xml file) that might override some
information? Can it be that not all classes are on the classpath? Or can there
be another persistence.xml or orm.xml on the classpath that can affect the
results? As there are plenty of tests that test an entity that extend a
is
by email and then delete it.
> -Original Message-
> From: tbee [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 24, 2007 10:20 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: Open JPA error-Could not locate metadata for the
> class using alias
>
>
"actual" (extending) class
containing the business logic?
How would one declare the narrowing?
Tom
--
View this message in context:
http://www.nabble.com/Open-JPA-error-Could-not-locate-metadata-for-the-class-using-alias-tf3561516.html#a10165713
Sent from the open-jpa-dev mailing list archive at Nabble.com.
ED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 24, 2007 9:40 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: Open JPA error-Could not locate metadata for the
> class using alias
>
> Hi tbee,
>
> I've only seen bits and pieces of this issue scattered
open-jpa-dev@incubator.apache.org
> Subject: Re: Open JPA error-Could not locate metadata for the
> class using alias
>
>
>
>
> Marina Vatkina wrote:
> >
> > The spec defines the following limitations of a MappedSuperclass:
> >
> > 2.1.9.2 Mapped Superclasses
l (because it knows the class in
question is persisted, but has trouble finding the metadata).
--
View this message in context:
http://www.nabble.com/Open-JPA-error-Could-not-locate-metadata-for-the-class-using-alias-tf3561516.html#a10165609
Sent from the open-jpa-dev mailing list archive at Nabble.com.
Hi tbee,
I've only seen bits and pieces of this issue scattered through a
dozen emails. I understand vaguely that you're trying to separate the
persistent field definition from the behavior, but can't really
understand how you're trying to do it.
Would it be possible for you to post a com
tbee wrote:
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.
I've tested this, but OpenJPA st
(@Entity
extends @Entity). It requires the superclass to be MappedSuperclass (@Entity
extends @MappedSuperclass).
So unforntunately this approach seems to be a dead end.
--
View this message in context:
http://www.nabble.com/Open-JPA-error-Could-not-locate-metadata-for-the-class-using-alias-tf3
essage in context:
http://www.nabble.com/Open-JPA-error-Could-not-locate-metadata-for-the-class-using-alias-tf3561516.html#a10113798
Sent from the open-jpa-dev mailing list archive at Nabble.com.
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
ed a class that
contains the reversed engineered mappings.
> They might, but that would be beyond the spec and as such not a portable
> solution.
If this is beyond the spec: what is @MappedSuperclass intended for?
--
View this message in context:
http://www.nabble.com/Open-JPA-error-Coul
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
ave an issue with lazy loading there, but the approach is perfect.
--
View this message in context:
http://www.nabble.com/Open-JPA-error-Could-not-locate-metadata-for-the-class-using-alias-tf3561516.html#a10106645
Sent from the open-jpa-dev mailing list archive at Nabble.com.
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
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";
roviderImpl
nl.reinders.bm.Contract
50x
nl.reinders.bm.Websort
--
View this message in context:
http://www.nabble.com/Open-JPA-error-Could-not-locate-metadata-for-the-class-using-alias-tf35
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
t 3); my persistent classes are reverse engineered from the DB and
some metatables generate classes that cause trouble, and I explicitely make
them non-persistent by removing them from the list. Sorry.
--
View this message in context:
http://www.nabble.com/Open-JPA-error-Could-not-locate-metadat
tring iDescription;
....
}
--
View this message in context:
http://www.nabble.com/Open-JPA-error-Could-not-locate-metadata-for-the-class-using-alias-tf3561516.html#a10101376
Sent from the open-jpa-dev mailing list archive at Nabble.com.
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
in context:
http://www.nabble.com/Open-JPA-error-Could-not-locate-metadata-for-the-class-using-alias-tf3561516.html#a10095774
Sent from the open-jpa-dev mailing list archive at Nabble.com.
error-Could not locate metadata for the class using
alias
Hi,
I am trying to run standalone application access the database using
spring ,openjpa.
part of code in main method
EntityManagerFactory factory =
Persistence.createEntityManagerFactory("tsf");
EA Systems
415.402.7317
-Original Message-
From: saidulu chitipolu [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 11, 2007 1:23 PM
To: open-jpa-dev@incubator.apache.org
Subject: Open JPA error-Could not locate metadata for the class using
alias
Hi,
I am trying to run standalone a
On 4/11/07, saidulu chitipolu <[EMAIL PROTECTED]> wrote:
your earliest suggetions are valuable
You may want to take a look at the following thread -
http://www.mail-archive.com/open-jpa-dev@incubator.apache.org/msg02770.html.
Make sure that your class is @Entity-annotated, PCEnhance it and
Hi,
I am trying to run standalone application access the database using spring
,openjpa.
part of code in main method
EntityManagerFactory factory = Persistence.createEntityManagerFactory("tsf");
EntityManager em = factory.createEntityManager();
Syst
46 matches
Mail list logo
