Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.de;
  h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
  b=ZoqjOiVLPEkWi6qRSS9fmkOPqlfGbgxn6j0Hi77h5wVTbXCZ+LmzDIZj9gr5ZXM2DEZEzm6L/7hcl2ufPSC5gr47O8Gt1fUS2w4AJJiywxEFhNuTWa+E4CMtblQCzVURUNDec5vxs5NNcpKjTmqoFRJ6dzyKZ3LM5pJ1PlbMJ7M=;
Date: Thu, 30 Oct 2008 08:40:01 +0000 (GMT)
From: Mark Struberg <struberg@yahoo.de>
Subject: multiple usage of @Embedded in one entity
To: dev@openjpa.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-ID: <709940.34205.qm@web27806.mail.ukl.yahoo.com>

Hi!

I have a JPA2.0 question.

I did find some discussion (better: complaints) about embedding members of =
the same class multiple times, but could not find the information about how=
 this will be solved in the JSR-317 draft. So maybe anyone can point me to =
some information about this.

I've used kodo for a long time, and I know that that the code already exist=
s and did work with JDO.

Here is my problem:

Imagine having a

@Embeddable
public class Address {
  private String zip;
  private String city;
  private String street;
  ...
}

and you like to use this Address multiple times in another entity:

@Entity
public class Customer {
  private String name
  @Embedded private Address deliveryAddress;
  @Embedded private Address invoiceAddress;
}

This does not work out as expected, since the created SQL does only generat=
e ONE set of the fields (and _silently_ skipping the 2nd Address!).
This can be worked around by using @AttributeOverrides, but you will get in=
to troubles if the Address also contains an embedded field (eg '@Embeddable=
 public class Contact' containing tel, fax, email) since you cannot control=
 these names via the attribute overrides anymore.

So, I'd like to know if it is likely that there is anything like=20
@Embedded(prefix=3D"INVOICE")
@Embedded(prefix=3D"DELIVER")
with an automated default mechanism like kodo-JDO had?


(and please don't argue that addresses should stored in a 1:n table anyway =
- this is only an example ;)

txs and LieGrue,
strub
=0A=0A=0A