>is there any technical advantage to this, or just the easthetic
>pleasure? :)
To me this is most important when developing in a team. Managing a
monolithic mapping file is very difficult if everyone is trying to
edit it at once. (But yeah, I do also find it improves the
aesthetics.)
>i was thin
On 19 Jul (11:25), Gavin_King/[EMAIL PROTECTED] wrote:
> I'd like to throw this up for discussion. Anybody disagree with any of
> these points or have any new ones?
>
> ==
>
> *Hibernate ''Best'' Practices
I agree with all of this
I'd like to throw this up for discussion. Anybody disagree with any of
these points or have any new ones?
==
*Hibernate ''Best'' Practices
***use fine grained objects
Write fine-grained classes and map them using || or
||. Use an |A