I'm reverse-engineering a pretty simple PostgreSQL database with hbm2java (via Maven).

There are a few tables which should be read-only -- e.g. lookup tables with fixed constant values in them.

Is there any way to indicate to the tool that it should generate no setters for the corresponding objects?

There's no actual safety problem since the database user only has SELECT granted on those tables, but my sense of neatness is offended by having setters that will always cause exceptions to be thrown.

Is this only achievable with a custom reverse engineering strategy?

Thanks,

Andrew.