Is there a way, or are there plans to incorporate, an annotationconfiguration strategy that searches the given classpath(s) for @Entity objects, and will use them instead of a list of <mapping class=...> within a cfg.xml?

If not, just let me know, and I'll write something dirty, and post it back here.

In jira we have tasks for using a Ejb3Configuration to get the same behavior as with EJB3, but that is still work in progress.

If you have something that can work as a cheap workaround until then
patches are welcome in jira.

I would propose additions to the hibernate-configuration-3.0.dtd, to make the following possible.



Where "include" elements would declare classes with wildcards to include, and "exclude" elements ignore those classes in the path. If the body of "mapping" is empty, all classes would be included.

This could also be applied to the "jar" and maybe "package" attributes, but I don't know enough about them. I also don't know the future of the ejbconfiguration, as you stated.

So let me know if you want me to proceed. If this is not dirty enough, I have another, dirtier idea.

it does not make sense to add that to hibernate-mapping.dtd....

Understood. I'll make something less sexy.