Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: open-jpa-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of plinskey@bea.com designates
 66.248.192.39 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: RE: Open JPA error-Could not locate metadata for the class using
 alias
Date: Tue, 24 Apr 2007 23:27:48 -0700
Message-ID: <7D856CDFE035FF45A0420ACBD71BDD630401B339@repbex02.amer.bea.com>
In-Reply-To: <10175078.post@talk.nabble.com>
Thread-Topic: Open JPA error-Could not locate metadata for the class using
 alias
Thread-Index: AceHAmwrYFmIXWdUSEy9BwCDgqVS5wAAFyKQ
References: <625027.94080.qm@web8510.mail.in.yahoo.com>
 <10095774.post@talk.nabble.com>
 <1b5bfeb50704200452y29780d0epf3eb7cbc0cb4c574@mail.gmail.com>
 <10100315.post@talk.nabble.com> <10101376.post@talk.nabble.com>
 <4628F3E9.3070302@sun.com> <10106645.post@talk.nabble.com>
 <46291CE1.4070507@Sun.COM> <10110227.post@talk.nabble.com>
 <4629410E.9060607@Sun.COM> <10155865.post@talk.nabble.com>
 <462E2E7C.7090107@sun.com> <10165609.post@talk.nabble.com>
 <7D856CDFE035FF45A0420ACBD71BDD6303FB5EE6@repbex02.amer.bea.com>
 <10174891.post@talk.nabble.com>
 <7D856CDFE035FF45A0420ACBD71BDD630401B332@repbex02.amer.bea.com>
 <10175078.post@talk.nabble.com>
From: "Patrick Linskey" <plinskey@bea.com>
To: <open-jpa-dev@incubator.apache.org>

Oh, and don't worry about the lack of the DB. We can probably
forward-generate a schema for Derby or somesuch that is good enough for
the purposes of tracking down this problem.

-Patrick

-- 
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,  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 it. 

> -----Original Message-----
> From: tbee [mailto:tbee@tbee.org] 
> Sent: Tuesday, April 24, 2007 11:24 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:
> > 
> > Could you try out the almost-final OpenJPA 0.9.7 bits instead? The 
> > candidate (currently being voted on) is at 
> > 
> http://people.apache.org/~mikedd/staging-repository/org/apache/openjpa
> > /o 
> > 
> penjpa-project/0.9.7-incubating/openjpa-project-0.9.7-incubati
> ng-binary.
> > zip
> > 
> > If that doesn't work out, could you package up an example for us to 
> > try out against the latest code?
> > 
> 
> 47  reinders  INFO   [main] openjpa.Runtime - Starting OpenJPA
> 0.9.7-incubating
> 172  reinders  INFO   [main] openjpa.jdbc.JDBC - Using 
> dictionary class
> "org.apache.openjpa.jdbc.sql.InformixDictionary".
> Exception in thread "main" <0.9.7-incubating fatal user error>
> org.apache.openjpa.persistence.ArgumentException: Could not 
> locate metadata for the class using alias "Article". 
> Registered alias mappings:
> "{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?
> 
> I can just "upload file" 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.
> 
> 

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 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.