You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by "Ueberbach, Michael" <mi...@dbh.de> on 2007/07/09 11:44:02 UTC
Problems using openJPA
Hello all,
I have some problems using openJPA with Geronimo V2 (M6RC1). The application (stateless session beans and entity beans) is written in EJB3-Style
using only annotations (persistence.xml is the only descriptor) and is deployed succesfully.
When trying to fetch some data the following exception is thrown
23:38:42,637 ERROR [OpenEJB] The bean instances business method encountered a system exception: Could not locate metadata for the class using alias "Person". This could mean that the OpenJPA enhancer or load-time weaver was not run on the type whose alias is "Person". Registered alias mappings: "{Person=null}"
<1.0.0-SNAPSHOT-SNAPSHOT fatal user error> org.apache.openjpa.persistence.ArgumentException: Could not locate metadata for the class using alias "Person". This could mean that the OpenJPA enhancer or load-time weaver was not run on the type whose alias is "Person". Registered alias mappings: "{Person=null}"
at org.apache.openjpa.meta.MetaDataRepository.getMetaData(MetaDataRepository.java:348)
(...)
("Person" is the name used in the @entity annotation for the entity bean.)
There are some other warnings before. But I do not really understand their importance and whether they are relying to the exception coming later.
First this one while deploying (coming a lot of times):
23:31:35,979 WARN [Runtime] The property named "openjpa.ClassTransformerOptions" was not recognized and will be ignored, although the name closely matches a valid property called "openjpa.ClassResolver".
Second this one while trying to fetch the data
23:38:41,410 WARN [Enhance] An exception was thrown while attempting to perform class file transformation on "de/lama/sample3/stammdaten/ejb/PersonBean":
<1.0.0-SNAPSHOT-SNAPSHOT nonfatal user error> org.apache.openjpa.util.UserException: Type "de.lama.sample3.stammdaten.ejb.PersonBean" attempts to use both field and property access. Only one access method is permitted.
This second warning seems strange to me because all used property getters are annotated and no private field has any annotation, so the access method
is clear.
Has someone an idea what's going wrong here?
Many thanks for any advice.
dbh Logistics IT AG
Michael Ueberbach
Software Management
Faulenstr. 31, 28195 Bremen
Fon: +49 421 30902-49
Fax: +49 421 30902-57
E-Mail: michael.ueberbach@dbh.de
Internet: www.dbh.de - www.plusmove.de <http://www.plusmove.de>
dbh Logistics IT AG, Sitz / Registered Office: Faulenstraße 31, 28195 Bremen, Deutschland / Germany
Registergericht / Companies' Register: Amtsgericht Bremen, HRB 20499
Vorstandsvorsitzender / Chief Executive Officer (CEO): Reimund Ott
Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board: Klaus Platz
Haftungsausschluss:
Diese Nachricht enthält vertrauliche Informationen und ist ausschließlich für den Adressaten bestimmt. Falls Sie die Daten irrtümlich erhalten haben, nehmen Sie bitte Kontakt mit dem Absender auf und löschen Sie die Daten auf jedem Computer und Datenträger. Die dbh Logistics IT AG ist nicht verantwortlich für die ordnungsgemäße, vollständige und verzögerungsfreie Übertragung der Nachricht. Der Inhalt der E-Mail ist nur rechtsverbindlich, wenn er unsererseits durch einen Brief oder ein Fax entsprechend bestätigt wird.
Exclusion of Liability:
This message contains confidential information and is destined for the recipient exclusively. Should you have received these data by mistake, please contact the originator and delete the data from all your computers and data storage media. dbh Logistics IT AG is not liable for the proper, complete and undelayed transmission of the message. The content of the e-mail is not legally binding, unless it is confirmed appropriately by a supplementary fax or letter from us.
AW: AW: Problems using openJPA
Posted by "Ueberbach, Michael" <mi...@dbh.de>.
Hello David,
To your last question: The SUN spec says
"In addition to returning and setting the persistent state of the instance, the property accessor methods
may contain other business logic as well, for example, to perform validation. The persistence provider
runtime executes this logic when property-based access is used."
openJPA follows this in offering the two possibilities of accessing. The openJPA manual says
"JPA offers two modes of persistent state access: field access, and property access.
To use property access, set your entity element's access attribute to PROPERTY, or place your metadata and mapping annotations on the getter method.
Each class must use either field access or property access for all state; you cannot use both access types within the same class."
The whole problem is that the described way to choose the property access by placing the annotations at the getter methods does not show any effects.
More worse openJPA throws an org.apache.openjpa.util.UserException (as described) and does not choose any of the two alternative ways.
This exceptions sounds as if the annotations set at the getter methods were not reckognized when parsing the entity classes. The question for me is:
Have I to do something more (or have I chosen the wrong annotations or what ever) to get this code working?
The test with jboss was done to see whether there also an error would be visible, but it was not. I agree that this gives no final security about the compliance of jboss. Indeed my aim is to get the thing working on geronimo/openJPA!
Thanks for any help
Michael
-----Ursprüngliche Nachricht-----
Von: David Jencks [mailto:david_jencks@yahoo.com]
Gesendet: Dienstag, 17. Juli 2007 23:30
An: user@geronimo.apache.org
Betreff: Re: AW: Problems using openJPA
On Jul 17, 2007, at 9:25 AM, Ueberbach, Michael wrote:
> Hi Jacek,
>
> I had to make a little break, now I'm trying to get back to the last
> situation.
>
> Following your last advices:
>
> reducing the persistance.xml to the neccessary elements works for
> deploying, but does not help in fetching data. In fact the same
> exception (...Could not locate metadata for the class ...) is thrown.
>
> I checked the code again:
> - no field is annotated
> - every getter is annotated (at least with @Basic)
> - every other method named with get... Is annotated @Transient
>
> Therefore the access type has to be clear (= PROPERTY).
> Nevertheless this is not recognized.
>
> So I've tried two things:
>
> First:
> I put a xml mapping file (orm.xml) inside the deployment jar, where I
> explicitly set the access type to PROPERTY for all classes.
> The deployment works, but the warning
>
> "<1.0.0-SNAPSHOT-SNAPSHOT nonfatal user error>
> org.apache.openjpa.util.UserException: Type
> "de.lama.sample3.stammdaten.ejb.PersonBean" attempts to use both field
> and property access. Only one access method is permitted."
>
> remains and the method call still doesn't work.
>
> Second:
> I deployed the whole stuff unchanged (except the deployment plan) to a
> jboss server(4.04) to compare the results. Here everything works as
> expected.
>
> As result it seems to me that if there isn't an error inside the
> deployed code that jboss does not find, there must be something wrong
> with parsing the classes annotations in geronimo resp. openjpa.
I haven't looked into your problem in detail, but I don't think you can conclude from hibernate's ability to deploy an app X that X is entirely spec compliant and can be deployed on all other compliant jpa implementations.
Out of curiousity why are you using property access? I have yet to understand why anyone would do this given a choice.... hoping for enlightenment.
thanks
david jencks
>
>
> regards
> Michael
>
>
> -----Ursprüngliche Nachricht-----
> Von: Ueberbach, Michael [mailto:michael.ueberbach@dbh.de]
> Gesendet: Dienstag, 10. Juli 2007 18:06
> An: user@geronimo.apache.org; jacek@laskowski.net.pl
> Betreff: AW: Problems using openJPA
>
> Hi Jacek,
>
> Thanks for your hints. To the first point: I've already seen this in
> the spec. I'm quite shure there is no access via the instance
> variables (but I will prove it again). I will also try to eliminate
> the entries in persistance.xml that are not neccessary. I'll tell the
> results as soon as possible.
>
> Michael
>
> -----Ursprüngliche Nachricht-----
> Von: eljotpl@gmail.com [mailto:eljotpl@gmail.com] Im Auftrag von Jacek
> Laskowski
> Gesendet: Dienstag, 10. Juli 2007 11:19
> An: user@geronimo.apache.org
> Betreff: Re: Problems using openJPA
>
> On 7/10/07, Ueberbach, Michael <mi...@dbh.de> wrote:
>> Hello Jacek,
>>
>> meanwhile I'm able to send the jar I deployed to geronimo. I attach
>> it to this mail, sources should be included. Also the persistence.xml
>> that is used.
>> As you can see I put @Basic annotations to all property getters
>> explicitly (although I think this should be default) to make shure
>> that access should be done by property (and not by field).
>> Nevertheless this seems not be recognized by openJPA. It would be
>> great if you have any idea why and what should be done.
>
> Hi Michael,
>
> I've just started looking into it, but thought I'd tell you that when
> you use property-based access (via getters) you should not access the
> entity state via instance fields.
>
> You don't need to specify vendor element in the persistence.xml file.
> Geronimo defaults to OpenJPA. According to the spec (6.2.1.4 provider
> p.135):
>
> The provider element must be specified if the application is dependent
> upon a particular persistence provider being used.
>
> You don't need to specify class elements in Java EE env (as opposed to
> Java SE env). The container looks for other files unless exclude-
> unlisted-classes element is specified (which is not the case in your
> example).
>
> See if that helps out. Going to spot other (mis)uses of the spec that
> might cause the trouble.
>
> Jacek
>
> --
> Jacek Laskowski
> http://www.JacekLaskowski.pl
Re: AW: Problems using openJPA
Posted by David Jencks <da...@yahoo.com>.
On Jul 17, 2007, at 9:25 AM, Ueberbach, Michael wrote:
> Hi Jacek,
>
> I had to make a little break, now I'm trying to get back to the
> last situation.
>
> Following your last advices:
>
> reducing the persistance.xml to the neccessary elements works for
> deploying, but does not help in fetching data. In fact the same
> exception
> (...Could not locate metadata for the class ...) is thrown.
>
> I checked the code again:
> - no field is annotated
> - every getter is annotated (at least with @Basic)
> - every other method named with get... Is annotated @Transient
>
> Therefore the access type has to be clear (= PROPERTY).
> Nevertheless this is not recognized.
>
> So I've tried two things:
>
> First:
> I put a xml mapping file (orm.xml) inside the deployment jar,
> where I explicitly set the access type to PROPERTY for all classes.
> The deployment works, but the warning
>
> "<1.0.0-SNAPSHOT-SNAPSHOT nonfatal user error>
> org.apache.openjpa.util.UserException: Type
> "de.lama.sample3.stammdaten.ejb.PersonBean" attempts to use both
> field and property access. Only one access method is permitted."
>
> remains and the method call still doesn't work.
>
> Second:
> I deployed the whole stuff unchanged (except the deployment plan)
> to a jboss server(4.04) to compare the results. Here everything
> works as expected.
>
> As result it seems to me that if there isn't an error inside the
> deployed code that jboss does not find, there must be something
> wrong with parsing the classes annotations in geronimo resp. openjpa.
I haven't looked into your problem in detail, but I don't think you
can conclude from hibernate's ability to deploy an app X that X is
entirely spec compliant and can be deployed on all other compliant
jpa implementations.
Out of curiousity why are you using property access? I have yet to
understand why anyone would do this given a choice.... hoping for
enlightenment.
thanks
david jencks
>
>
> regards
> Michael
>
>
> -----Ursprüngliche Nachricht-----
> Von: Ueberbach, Michael [mailto:michael.ueberbach@dbh.de]
> Gesendet: Dienstag, 10. Juli 2007 18:06
> An: user@geronimo.apache.org; jacek@laskowski.net.pl
> Betreff: AW: Problems using openJPA
>
> Hi Jacek,
>
> Thanks for your hints. To the first point: I've already seen this
> in the spec. I'm quite shure there is no access via the instance
> variables (but I will prove it again). I will also try to eliminate
> the entries in persistance.xml that are not neccessary. I'll tell
> the results as soon as possible.
>
> Michael
>
> -----Ursprüngliche Nachricht-----
> Von: eljotpl@gmail.com [mailto:eljotpl@gmail.com] Im Auftrag von
> Jacek Laskowski
> Gesendet: Dienstag, 10. Juli 2007 11:19
> An: user@geronimo.apache.org
> Betreff: Re: Problems using openJPA
>
> On 7/10/07, Ueberbach, Michael <mi...@dbh.de> wrote:
>> Hello Jacek,
>>
>> meanwhile I'm able to send the jar I deployed to geronimo. I
>> attach it to this mail, sources should be included. Also the
>> persistence.xml that is used.
>> As you can see I put @Basic annotations to all property getters
>> explicitly (although I think this should be default) to make shure
>> that access should be done by property (and not by field).
>> Nevertheless this seems not be recognized by openJPA. It would be
>> great if you have any idea why and what should be done.
>
> Hi Michael,
>
> I've just started looking into it, but thought I'd tell you that
> when you use property-based access (via getters) you should not
> access the entity state via instance fields.
>
> You don't need to specify vendor element in the persistence.xml file.
> Geronimo defaults to OpenJPA. According to the spec (6.2.1.4 provider
> p.135):
>
> The provider element must be specified if the application is
> dependent upon a particular persistence provider being used.
>
> You don't need to specify class elements in Java EE env (as opposed
> to Java SE env). The container looks for other files unless exclude-
> unlisted-classes element is specified (which is not the case in
> your example).
>
> See if that helps out. Going to spot other (mis)uses of the spec
> that might cause the trouble.
>
> Jacek
>
> --
> Jacek Laskowski
> http://www.JacekLaskowski.pl
AW: Problems using openJPA
Posted by "Ueberbach, Michael" <mi...@dbh.de>.
Hi Jacek,
I had to make a little break, now I'm trying to get back to the last situation.
Following your last advices:
reducing the persistance.xml to the neccessary elements works for deploying, but does not help in fetching data. In fact the same exception
(...Could not locate metadata for the class ...) is thrown.
I checked the code again:
- no field is annotated
- every getter is annotated (at least with @Basic)
- every other method named with get... Is annotated @Transient
Therefore the access type has to be clear (= PROPERTY). Nevertheless this is not recognized.
So I've tried two things:
First:
I put a xml mapping file (orm.xml) inside the deployment jar, where I explicitly set the access type to PROPERTY for all classes.
The deployment works, but the warning
"<1.0.0-SNAPSHOT-SNAPSHOT nonfatal user error> org.apache.openjpa.util.UserException: Type "de.lama.sample3.stammdaten.ejb.PersonBean" attempts to use both field and property access. Only one access method is permitted."
remains and the method call still doesn't work.
Second:
I deployed the whole stuff unchanged (except the deployment plan) to a jboss server(4.04) to compare the results. Here everything works as expected.
As result it seems to me that if there isn't an error inside the deployed code that jboss does not find, there must be something wrong with parsing the classes annotations in geronimo resp. openjpa.
regards
Michael
-----Ursprüngliche Nachricht-----
Von: Ueberbach, Michael [mailto:michael.ueberbach@dbh.de]
Gesendet: Dienstag, 10. Juli 2007 18:06
An: user@geronimo.apache.org; jacek@laskowski.net.pl
Betreff: AW: Problems using openJPA
Hi Jacek,
Thanks for your hints. To the first point: I've already seen this in the spec. I'm quite shure there is no access via the instance variables (but I will prove it again). I will also try to eliminate the entries in persistance.xml that are not neccessary. I'll tell the results as soon as possible.
Michael
-----Ursprüngliche Nachricht-----
Von: eljotpl@gmail.com [mailto:eljotpl@gmail.com] Im Auftrag von Jacek Laskowski
Gesendet: Dienstag, 10. Juli 2007 11:19
An: user@geronimo.apache.org
Betreff: Re: Problems using openJPA
On 7/10/07, Ueberbach, Michael <mi...@dbh.de> wrote:
> Hello Jacek,
>
> meanwhile I'm able to send the jar I deployed to geronimo. I attach it to this mail, sources should be included. Also the persistence.xml that is used.
> As you can see I put @Basic annotations to all property getters explicitly (although I think this should be default) to make shure that access should be done by property (and not by field). Nevertheless this seems not be recognized by openJPA. It would be great if you have any idea why and what should be done.
Hi Michael,
I've just started looking into it, but thought I'd tell you that when you use property-based access (via getters) you should not access the entity state via instance fields.
You don't need to specify vendor element in the persistence.xml file.
Geronimo defaults to OpenJPA. According to the spec (6.2.1.4 provider
p.135):
The provider element must be specified if the application is dependent upon a particular persistence provider being used.
You don't need to specify class elements in Java EE env (as opposed to Java SE env). The container looks for other files unless exclude-unlisted-classes element is specified (which is not the case in your example).
See if that helps out. Going to spot other (mis)uses of the spec that might cause the trouble.
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
AW: Problems using openJPA
Posted by "Ueberbach, Michael" <mi...@dbh.de>.
Hi Jacek,
Thanks for your hints. To the first point: I've already seen this in the spec. I'm quite shure there is no access via the instance variables (but I will prove it again). I will also try to eliminate the entries in persistance.xml that are not neccessary. I'll tell the results as soon as possible.
Michael
-----Ursprüngliche Nachricht-----
Von: eljotpl@gmail.com [mailto:eljotpl@gmail.com] Im Auftrag von Jacek Laskowski
Gesendet: Dienstag, 10. Juli 2007 11:19
An: user@geronimo.apache.org
Betreff: Re: Problems using openJPA
On 7/10/07, Ueberbach, Michael <mi...@dbh.de> wrote:
> Hello Jacek,
>
> meanwhile I'm able to send the jar I deployed to geronimo. I attach it to this mail, sources should be included. Also the persistence.xml that is used.
> As you can see I put @Basic annotations to all property getters explicitly (although I think this should be default) to make shure that access should be done by property (and not by field). Nevertheless this seems not be recognized by openJPA. It would be great if you have any idea why and what should be done.
Hi Michael,
I've just started looking into it, but thought I'd tell you that when you use property-based access (via getters) you should not access the entity state via instance fields.
You don't need to specify vendor element in the persistence.xml file.
Geronimo defaults to OpenJPA. According to the spec (6.2.1.4 provider
p.135):
The provider element must be specified if the application is dependent upon a particular persistence provider being used.
You don't need to specify class elements in Java EE env (as opposed to Java SE env). The container looks for other files unless exclude-unlisted-classes element is specified (which is not the case in your example).
See if that helps out. Going to spot other (mis)uses of the spec that might cause the trouble.
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
Re: Problems using openJPA
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 7/10/07, Ueberbach, Michael <mi...@dbh.de> wrote:
> Hello Jacek,
>
> meanwhile I'm able to send the jar I deployed to geronimo. I attach it to this mail, sources should be included. Also the persistence.xml that is used.
> As you can see I put @Basic annotations to all property getters explicitly (although I think this should be default) to make shure that access should be done by property (and not by field). Nevertheless this seems not be recognized by openJPA. It would be great if you have any idea why and what should be done.
Hi Michael,
I've just started looking into it, but thought I'd tell you that when
you use property-based access (via getters) you should not access the
entity state via instance fields.
You don't need to specify vendor element in the persistence.xml file.
Geronimo defaults to OpenJPA. According to the spec (6.2.1.4 provider
p.135):
The provider element must be specified if the application is dependent
upon a particular persistence provider being used.
You don't need to specify class elements in Java EE env (as opposed to
Java SE env). The container looks for other files unless
exclude-unlisted-classes element is specified (which is not the case
in your example).
See if that helps out. Going to spot other (mis)uses of the spec that
might cause the trouble.
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
AW: Problems using openJPA
Posted by "Ueberbach, Michael" <mi...@dbh.de>.
Hello Jacek,
Thanks for the prompt answer. I will send the jar as soon as possible. Unfortunately I'm at the moment not at my used workplace.
Regards
Michael
-----Ursprüngliche Nachricht-----
Von: eljotpl@gmail.com [mailto:eljotpl@gmail.com] Im Auftrag von Jacek Laskowski
Gesendet: Montag, 9. Juli 2007 11:49
An: user@geronimo.apache.org
Betreff: Re: Problems using openJPA
On 7/9/07, Ueberbach, Michael <mi...@dbh.de> wrote:
> 23:38:42,637 ERROR [OpenEJB] The bean instances business method
> encountered a system exception: Could not locate metadata for the
> class using alias "Person". This could mean that the OpenJPA enhancer
> or load-time weaver was not run on the type whose alias is "Person". Registered alias mappings:
> "{Person=null}"
...
> First this one while deploying (coming a lot of times):
> 23:31:35,979 WARN [Runtime] The property named
> "openjpa.ClassTransformerOptions" was not recognized and will be
> ignored, although the name closely matches a valid property called
> "openjpa.ClassResolver".
Ignore it.
> 23:38:41,410 WARN [Enhance] An exception was thrown while attempting
> to perform class file transformation on
> "de/lama/sample3/stammdaten/ejb/PersonBean":
>
> <1.0.0-SNAPSHOT-SNAPSHOT nonfatal user error>
> org.apache.openjpa.util.UserException: Type
> "de.lama.sample3.stammdaten.ejb.PersonBean" attempts to use both field
> and property access. Only one access method is permitted.
That's the culprit. Could you publish the entity jar you deployed to Geronimo. I think that Geronimo doesn't add much to it - OpenJPA (the default JPA provider) can't do its job and complains and so does Geronimo.
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
Re: Problems using openJPA
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 7/9/07, Ueberbach, Michael <mi...@dbh.de> wrote:
> 23:38:42,637 ERROR [OpenEJB] The bean instances business method encountered
> a system exception: Could not locate metadata for the class using alias
> "Person". This could mean that the OpenJPA enhancer or load-time weaver was
> not run on the type whose alias is "Person". Registered alias mappings:
> "{Person=null}"
...
> First this one while deploying (coming a lot of times):
> 23:31:35,979 WARN [Runtime] The property named
> "openjpa.ClassTransformerOptions" was not recognized and will be ignored,
> although the name closely matches a valid property called
> "openjpa.ClassResolver".
Ignore it.
> 23:38:41,410 WARN [Enhance] An exception was thrown while attempting to
> perform class file transformation on
> "de/lama/sample3/stammdaten/ejb/PersonBean":
>
> <1.0.0-SNAPSHOT-SNAPSHOT nonfatal user error>
> org.apache.openjpa.util.UserException: Type
> "de.lama.sample3.stammdaten.ejb.PersonBean" attempts to use
> both field and property access. Only one access method is permitted.
That's the culprit. Could you publish the entity jar you deployed to
Geronimo. I think that Geronimo doesn't add much to it - OpenJPA (the
default JPA provider) can't do its job and complains and so does
Geronimo.
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl