[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4552?page=c...
]
Steve Ebersole commented on HHH-4552:
-------------------------------------
Paul, maybe an example is the best description...
Consider a component:
{code}
public class EmployeePK {
private String payrollNumber;
private String departmentCode;
}
{code}
HHH-2060 is about allowing to define a generator which constructs and returns EmployeePK
instances.
HHH-4552 (this issue) is about allowing to define a generator for the individual
properties in a composite identifier. So for example, to say that
"payrollNumber" is generated by some generator. This is needed because of the
SpecJ committee, retards that they seem to be, and how they mis-interpret the JPA2 spec
because it does not explicitly disallow doing this.
Support generated value within composite keys
---------------------------------------------
Key: HHH-4552
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4552
Project: Hibernate Core
Issue Type: Improvement
Components: annotations, core, metamodel
Affects Versions: 3.5.0-Beta-2
Reporter: Ståle W. Pedersen
Assignee: Steve Ebersole
Fix For: 3.5
Attachments: annotations.diff, annotations2.diff, core.diff, core2.diff,
test_idclassgeneratedvalue.tar.gz, test_idclassgeneratedvalue2.tar.gz
To ensure compatibility/portability with other jpa implementations hibernate need support
for generated value for composite keys. The SpecjEnterprise2010 application require this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira