Unfortunately, this looks to be a long-standing (forever?) problem. Whether you want to say this is a documentation error or a code deficiency, it's in the eye of the beholder. :-) From what I can tell from the history of this PropertiesReverseCustomizer, "collection" has never been a valid table type. Somebody got ahead of themselves with this documentation...
You are encouraged to open a JIRA for this issue. But, to be honest, unless you are ready and willing to dive into resolving it in the near term, other JIRAs will probably take priority. I may be mistaken and some OpenJPA developer may have reverse mapping as a "pet project"... Just trying to set the expectations. Thanks for finding the issue and I hope you follow through by creating a JIRA. If you don't want to or can't utilize the JIRA system, let us know so that we can file the problem report. Thanks, Kevin On Wed, Sep 14, 2011 at 10:40 AM, M. Spiro <m.sp...@dcs-caesar.de> wrote: > Hi, > > I'm using OpenJPA Reverse Mapping Tool in my current project and find it > very useful. However there's one documented functionality that is obviously > missing in the OpenJPA 2.x versions. > > According to the docs (Part 3, chapter 7, paragraph 2.1) a table can be > declared as collection table. I would expect that in this case a Java class > annotated as @Embeddable is created. I've made a test and declared a table > as "collection", but got an error message from the tool. I checked the > source code of org.apache.openjpa.jdbc.meta.PropertiesReverseCustomizer > (versions 2.1.0 and 2.1.1) and found out that the value "collection" is not > a valid one for the table type and leads to an IllegalArgumentException. > > Is there a way to generate classes from the collection tables? Or > generally, > is it possible to generate Embeddables with the reverse mapping tool? Was > it > possible in any older OpenJPA version? > > Kind regards, > Michael Spiro > >
