Hi,

Has anyone ever come across the idea of hibernate mapping just using the up-coming metadata in JDK 1.5? I don't mean doing things like using xdoclet -- generating mapping files according to metadata -- in that case, you still have to keep an eye on the mapping file, worrying about misplacing it. I mean hibernate could genuinely treat the jdk1.5 metadata as the mapping itself, thus it really achieves putting-one-thing-at-one-place.

Wouldn't it be great that we don't even have to write the separated xml mapping files? (Although, we might still have to write the configuration file, but I guess 99% of the time is spent on the mapping files)

The user would only have to specify the CLASSes instead of the MAPPING FILEs in the configuration file. This will be great for both users and tool-makers.

Sorry I didn't give a very serious thought about the feasibility. However, I think since the current xml mapping file is organized on a class-members basis, which is exactly how the metadata is organized. This would give a very strong support for migration.

Any deas?

I'm currently implementing this feature.

Oh that sounds great! Does this require a big revamp on hibernate or it's just a touch-up? Is there any set schedule of the release of this feature?

________
nick

It will be on top of Hibernate3 and won't change any part (or minimal) of Hibernate core.
No schedule except it will be done when it will :)

I saw gavin's blog today also, thumbs up!!

Could you please point me to this particular blog? I couldn't find it - Thanks!

This is summarized here http://www.hibernate.org/200.html