Hibernate version: hibernate-annotations 3.3.1, hibernate-commons-annotations 3.3.0.ga, hibernate-entitymanager3.3.2, hibernate-core 3.2

Name and version of the database you are using: Orcale XE 10g Release 2 (10.2)

I am using Hibernate Tools 3.2.2.Beta1 with Eclipse 3.3.2

Is there a way to tell the reverse engineering process in the Hibernate Tools plugin for Eclipse to generate "protected" setters via the reveng.xml file or a custom ReverseEngineering Strategy?

Thanks!

yes, reveng.xml supports adding <meta> tags and the same does the programmatic strategy.

Just set in reveng.xml <meta attribute="scope-set">protected</meta>

or return a properties set with scope-set = protected.

Max,

Thanks for reply to my post.

When I first added this tag it didn't work for me because I was trying to add it inside the column tag of the table tag, like so:


But I see now it only works out side of the column tag, like so:


This works great when you are not extending a Base Class. However when you are extending a Base Class that defines the setter method for the id as private and defines the getter method for the id as public, how do you tell hibernate not to generate the setter method for the id and to delegate the getter method for the id?

I am guessing to accomplish this, one would have to implement a custom programmatic solution or strategy. I never implemented a programmatic strategy before, but feel I can do it if I had good instructions.


Thanks!

Just wanted to added that my mapping strategy is "one table per concrete class". Maybe this is not the best mapping strategy for me to use; since I am trying to extend a base class and then delegate my SomeClass.getID() method to BaseClass.getID() method and set my SomeClass.setID() method to private. Although I am still very interested in implement a custom programmatic solution or strategy to accomplish this, I am now conisdering implementing another mapping strategy that suites my needs.


Any suggestion is welcomed!

Thanks!

After reviewing the four different mapping strategies, Map one table per concrete class, Map one table per concrete class with union-subclass mapping, Map one table per class hierarchy, and Map one table per subclass, I still want to stick to the Map one table per concrete class mapping because its the most simplist and efficient.

With that being said, how do I implement a custom programmatic solution or strategy to accomplish delegating my getID() method to my super getID() method and how do I tell hibernate to omit the setID() method in my subclass because it is already implemented in my superclass setID() method?

Thanks Again!

I think I will try playing around with the template. See Hibernate Reference Guide 6.1.2.1. I basically want the pojo/PojoPropertyAccessor.ftl template file to detemine if there is an extended class for the pojo and if so, use the extended class to determine when and how to include the property accessor methods to the pojo.

I am new to Hibernate Tools and even more new to FreeMarker. Any help in figuring out this logic is much appreciated.

Thanks!

the simplest method:

Assume the method is always is called setID and just check in the .ftl file that when you bump into that property that you skip the generation or do something else special.

the advanced/complete method:

use toolclass property (see doc for that) to get access to a utility class of yours that uses reflection to load the base class and checks if it has the method already and then do the generation based on that.

Max,

Thanks to your advise I am able to create my POJOs they I prefer to.

Thanks!