We used the annotations approach. It worked fine, but we did find a
problem with them. We have several diffferent projects that use a
different subset of the model. If you use annotations to define
relationships, then you cannot re-use the object model java code
unless you configure hibernate to use all of it. If Object A relates
to Object B, but you only import Object A's configuration because
project 2 doesn't use Object B, Hibernate will complain.
The advantage of mapping (which we lost) is that you can have a truly
neutral object model, and if you aren't using certain relationships,
you don't have to include them - those methods will simply have empty
sets. But if that is not an issue, go right ahead. FDS doesn't even
know about the metadata - it maps objects to actionscript agnostically.
regards,
Christian.
On May 10, 2007, at 1:59 PM, Kevin wrote:
Does the built-in FDS / HibernateAssembler require the hbm.xml
mapping files in order to work properly OR can we use the annotations
approach? The only reason I ask is that I have not seen any examples
of people using Hibernate annotations.
According to Hibernate:
http://annotations.hibernate.org/
"As an option, you can now use JDK 5.0 annotations for object/
relational mapping with Hibernate 3.2. You can use annotations in
addition to or as a replacement of XML mapping metadata."
Is there a reason that this approach would not work with FDS? Does
FDS care where Hibernate gets it's metadata?
Thanks,
- Kevin
christian gruber + [EMAIL PROTECTED] + bus 905.640.1119 + mob
416.998.6023
process coach and architect + ISRÁFÍL CONSULTING SERVICES
