Hi,

I'm a newbie to Hibernate and I'm trying to figure how to modify the ReverseEngineeringStrategy to achieve customization of the generated code.

Here's what I've done so far:

• Created CustomStrategy which extends DelegatingReverseEngineeringStrategy
• Appended "Entity" to all table class names using an override on .tableToClassName(TableIdentifier tableIdentifier)
• Set the identifier strategy to "native" using an override on .getTableIdentifierStrategyName(TableIdentifier tableIdentifier)
• Translated all PK column names to "id" using an override on .columnToPropertyName(TableIdentifier table, String column)

And here's my wish list / questions that I can't figure out how/whether I can:

• Debug the reverse engineering / set break points to debug how my custom ReverseEngineeringStrategy works / what it does?
• At least add custom logging (either to System.out or log4j)? I tried both and I don't seem to be able to find any output anywhere.
• Generate all FKs with "lazy" fetching. Right now I have "select" everywhere.
• Distinguish between Views and Tables, in particular append "Entity" to every class based on a table (done that already) and "View" to every class based on a view.
• Teach Hibernate not to make up composite PKs for database views.
• Make Entity classes implement one interface (e.g. HibernateEntity), and View classes implement another one (HibernateView). I would create these interfaces on my own.
• Make Entity classes extend one class (e.g. HibernateEntityImpl), and View classes extended another one (e.g. HibernateViewImpl). I would create these classes on my own and provide some basic functionality.
• Make each class have a constructor that takes values for all properties (but not many-to-one relationships)
• Enable "dynamic-insert" and "dynamic-update" on all tables
• Have an enumeration of field names/properties in every class (e.g. called "public enum Fields")
• Have a list/hashmap of properties on top of the "single properties" (getters, setters)
• Have a clone method that automatically assigns all properties from one object to another

I understand that I can control a lot through the .hbm <meta> attributes. But I don't quite understand how can set those attributes through the ReverseEngineeringStrategy.

Please let me know.

Thanks in advance!

Is there really nobody who can provide any feedback on any of the questions above? :(

Hi,

I unfortunately can't check every forum for every question every day so sometimes things slide through...i'll try and make a stab at this



modifying reverse engineering strategy isn't really for newbies so I hope you are a bit more experience with hibernate than that ;)



you are on a roll ;)



To do this you would need to either use Ant in debug mode and connect a debugger or run eclipse in debug mode and connect a separate instance to it.



If you dont see any output i'll assume you are using the eclipse plugins and not the ant tasks. The logging goes to the error log view all controlled by log4j.properties in the hibernate plugins; and if you use system.out it should go to standard out of eclipse which should be visible if you run eclipse with -debug or -console.



select *is* lazy.



That information is not directly available. Hibernate's metamodel doesn't really have that distinguished. You'll need to query the database for that info or somehow be able to recognize that by some other means (i.e. naming)



You simply then just need to provide a primary key it should use - use reveng.xml for that or implement getPrimaryKeyColumnNames to make a better suggestion.



Why ?

Anyway - implement tableToMetaAttributes and you can tell which interfaces/classes there should be extended. See hibernate tools docs on which attributes to use.



See above.



hmm - thats tricky; but this is not part of reverse engineering - that is part of code generation.

If the current minimal and full constructors does not cut if for you then you probably need to have a custom pojo/PojoConstructors.ftl template
and have it do or call out to your own utility class that figures out which fields you want included.



Not directly supported in reverse engineering. If you really need that then you'll need to force than in the templates for hbm.xml or pojo's.



that's a very bad design IMO. just use reflection if you really need that.

Or if you really want that metadata statically available and possibly changing between releases and leaking into your layers then
generate a separate class/enum with this information. Simply have an additional hbm2java generation that uses your custom template and
not the default one that generate entities.



I don't undrestand what this is - but I think my answer would be the same as the previous one.



Sounds *very* dangerous - be sure you don't just assign associations and collections blindly and accidentally mix up objects from different sessions or object graphs.



implement (table|column)ToMetaAttributes.

p.s. i'll be faster to react to such questions if answer on JBoss Tools forum ;)

Thanks in advance![/quote]