Return-Path: 
 <dev-return-8094-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org>
Delivered-To: apmail-openjpa-dev-archive@www.apache.org
Received: (qmail 3412 invoked from network); 12 May 2008 22:10:31 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 12 May 2008 22:10:31 -0000
Received: (qmail 21596 invoked by uid 500); 12 May 2008 22:10:33 -0000
Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org
Received: (qmail 21424 invoked by uid 500); 12 May 2008 22:10:32 -0000
Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@openjpa.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@openjpa.apache.org>
List-Post: <mailto:dev@openjpa.apache.org>
List-Id: <dev.openjpa.apache.org>
Reply-To: dev@openjpa.apache.org
Delivered-To: mailing list dev@openjpa.apache.org
Received: (qmail 21413 invoked by uid 99); 12 May 2008 22:10:32 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 May 2008 15:10:32 -0700
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 May 2008 22:09:35 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id B85F3234C114
	for <dev@openjpa.apache.org>; Mon, 12 May 2008 15:09:55 -0700 (PDT)
Message-ID: <1943324274.1210630195754.JavaMail.jira@brutus>
Date: Mon, 12 May 2008 15:09:55 -0700 (PDT)
From: "Patrick Linskey (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Updated: (OPENJPA-593) Embedded element/key/value types
 should not be limited to simple fields and direct relations to other
 persistent types, but allow embedded Collections
In-Reply-To: <1938317102.1210180737397.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/jira/browse/OPENJPA-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Linskey updated OPENJPA-593:
------------------------------------

    Fix Version/s:     (was: 1.1.0)
                   1.2.0

> Embedded element/key/value types should not be limited to simple fields and direct relations to other persistent types, but allow embedded Collections
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-593
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-593
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: jdbc
>    Affects Versions: 1.1.0
>            Reporter: Michael Vorburger
>             Fix For: 1.2.0
>
>
> It's a pitty that @PersistentCollection(elementEmbedded = true) only works to to "depth 1", that is you can apparently not have an @Entity class A { @PersistentCollection(elementEmbedded=true) private Set<B> bs = new HashSet<B>(); ... } with @Entity class B again a  { @PersistentCollection(elementEmbedded=true) private Set<C> bs = new HashSet<C>(); ... }.
> On OpenJPA 1.1, this leads to the error: "org.apache.openjpa.util.MetaDataException: "X.y<element:class Y>" is mapped as embedded, but embedded field "..." is not embeddable.  Embedded element/key/value types are limited to simple fields and direct relations to other persistent types."
> The expected outcome would to have a schema with an SQL table A, an A_B (that works already!), and an A_B_C table (that doesn't work).
> JPA 2.0 JSR 317 <http://jcp.org/en/jsr/detail?id=317> says "... support for collections of embedded objects, multiple levels of embedded objects ..."  so may this will be supported 'soon-ish' (that one liner may not refer to this exact use case)?
> PS: This limitation has unfortunately turned into a show stopper for our use of OpenJPA, and made us look at another ORM which seems to support this kind of mapping.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.