Hi!
I've committed initial CUD-support for collections in the v22branch.
Now you can have ,, and the new
in the
,,, etc. elements.
Note: there are not support for callable statements (yet) - so no
support for Stored procedures yet.
Should not be big thing to add ...patches are welcome
/max
+1 to solution 1. But man it's verbose! I'd rather use the xml files instead
;-)
Ara.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:hibernate-devel-
> [EMAIL PROTECTED] On Behalf Of Emmanuel Bernard
> Sent: Saturday, May 01, 2004 2:58 PM
> Cc: [EMAIL PROTECTED]
> Subject: Re: [Hi
Emmanuel,
Composition would be my preferred approach.
I agree that the flat representation of XDoclet is less intuitive.
Cheers David.
- Original Message -
From: "Emmanuel Bernard" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, May 01, 2004 7:03 PM
Subject: [Hibernate] An
From the spec FAQ
*Why don't you support attribute subtyping (where one attribute type
extends another)?*
It complicates the attribute type system, and makes it much more
difficult to write "Specific Tools" (per the taxonomy in Section VI).
but it's more difficult to write annotation too...
Hi Bernard,
Your questions first: yes - I would think the compositional way is best
- mainly because it would mimic the hbm.xml way of declaring things.
Then now my complaints ;)
I must say that these annotations for sure is very verbatim and IMHO
clogs up the code - but hey, that's just me ;)
Note that the 'used' param is not... used / visible in a correct
annotation usage.
Emmanuel Bernard wrote:
OK here are more details.
Here is a typical correct annotation in the solution 1
@Map(
@Index(
type = "String"
),
@Element(
type="String"
columns = { @Column(
OK here are more details.
Here is a typical correct annotation in the solution 1
@Map(
@Index(
type = "String"
),
@Element(
type="String"
columns = { @Column( name = "FLD_ELT" ) }
),
@Key ( columns = { @Column( name = "PARENT_ID" ) } ),
table = "CHILDREN",
Hi Bernard,
I'm not totally fluent in JSR-175, yet - so I would very much appreciate
if you could give a more "full" examplesomething where you show the
complete method/class declaration (just the declaration, not the body) -
then I would have a much better grasp on what you're asking for -
I'm working on collection annotations right now, and I don't like the
way it goes.
Since now I managed to annotate using composition for dependent annotation
@Id (
@Generator(
@Param[]
)
)
And I strongly believe it's the best way to do.
But for collections, this is more complex.
The
