Max, I need some assistence to make your code running for our project's scenario.

The following issues are not solved:
- given template dir is not considered
- package cannot be passed in cfg2java mode: as a result no package declaration
- I don't want to walk thru all of my hbm's and put meta-tags there; instead I need to control rendering on "global" scope, i. e. for ALL classes

Please let me know adequate strategy to implement this.
javadoc in Cfg2JavaTool says "this class contains alot of helper methods. Consider wrapping PersistentClass and Component instead."

what exactly is the idea?
Do I need to overwrite PersistentClass and build a customized hibernate3.jar?

which template dir ? on ant tasks ? - add a jira with more details

package is not for cfg2java it should be on the jdbcconfiguration which it is AFAIK. cfg2java/hbm2java just dumps what is in the configuration - jdbcconfiguration is the one that should add the packagenames.

metatags generation - add a jira for it (should be very doable for you do to do via modifying the templates, but for that template dir must work for you .)

the comments idea is to provide a common class, lets call it POJOClass which wraps the PersistentClass which has the related methods instead of this static clutch of a helper...

package-issue is resolved, but I'm still struggling with the controller issue.

Basically what I need is some way to tell pass a controller-variable to the velocity engine.
This could possibly be done by passing a properties-file and accessing it thru the existing variables
OR
extending/wrapping some existing hibernate/hibernate-tools class providing this functionality. The problem is I am new to this area and I need some hints/given strategy to realize it in a reasonable time.

the simplest way to do this is to put some variables in your hibernate.properties or hibernate.cfg.xml these should be available from the cfg/Configuration object.

If you need more than just values, then we want to provide a way for the user to state that he wants THIS class instantiated and put it under THAT name in the template context - this is not done yet, but patches will be welcome.

The code that puts the basic stuff in the template is at TemplateHelper.init() - look around and see if you can find a way to pass enough info to this one and let it create your controller objects.