[hibernate-issues] [Hibernate-JIRA] Closed: (HBX-586) hbm2java (ejb3) should be create purely "ejb3 annotations" without "hibernate annotations"
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-586?page=all ]
Max Rydahl Andersen closed HBX-586:
-----------------------------------
Resolution: Rejected
concrete case is not an issue.
generally we should of course try and keep the codegen within the boundaries of the spec
but it won't be possible in all cases.
hbm2java (ejb3) should be create purely "ejb3 annotations"
without "hibernate annotations"
------------------------------------------------------------------------------------------
Key: HBX-586
URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-586
Project: Hibernate Tools
Type: Bug
Components: hbm2java
Versions: 3.1beta2
Environment: WinXP, Java5, JBossAS4.0.3SP1
Reporter: juanwang
With hibernate code generation "hbm2java(ejb3)" creates codes like e.g.:
<hbm2java jdk5="true" ejb3="true"></hbm2java>
@OneToMany(cascade={}, fetch=FetchType.LAZY)
@JoinColumn(name="funds_id", unique=false, nullable=true, insertable=true,
updatable=false)
@Cascade( {CascadeType.ALL, CascadeType.DELETE_ORPHAN} )
public Set<InfondsFundsBenchmark> getBenchmarks() {
return this.benchmarks;
}
But the annotation "@Cascade" runs not in ejb3 environment, because it is a
"hibernate annotation".
--
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