I'm trying to map my table names to particular class names in reveng.xml, but hbm2Java appears to be ignoring these settings. Am I doing something wrong?


When I generate my POJOs, they are coming out as SmsAggregator, SmsCarrier, etc., rather than the class names I designated in reveng.xml. Hbm2Java appears to be picking up all the other settings correctly (<table-filter>). What am I doing wrong here?

Figured it out. Apparantly, the catalog attribute of the table element is not optional when attempting to remap class names in this manner. I had tried using the "schema" attribute, but that didn't work. Apparantly for MySQL, you have to use "catalog" instead.

...but then again, I was never very clear on the difference between a "Schema" and a "Catalog".

Looks like I spoke too soon. The Class names being generated are now correct, but "foreign-key" properties that use these classes are being incorrectly named. (perhaps "incorrectly" is the wrong word).

For example, I got hbm2java to create the Aggregator class from the SMS_Aggregator table, but a field of type "Aggregator" in another class will still be called smsAggregator.

Any ideas?

This is one of the areas where there is not only no standard, but database vendors are handling things completely differently.

Most vendors use "schema" for a bunch of tables, and "catalog" for the area where the metadata on that table (such as name, column types, etc.) are stored.
However, "bunch of tables" may be all tables owned by a user, or all tables in something called a "database" (which can become a somewhat vague term in the presence of clustered databases).
Most vendors associate a schema with each user. I dimly remember that some database allowed a user to own multiple schemas, and the list of all schemas for that user would then be a "catalog" in the sense that Hibernate Tools uses the term, not in the usual "repository of metadata for a schema" sense.

It's all a real mess, and you're not alone in not being quite clear. The best thing you can do is to learn the terminology of your vendor, and how it applies to Hibernate Tools.

(What Hibernate Tools could do is to associate an explanation with the terms "catalog" and "schema" for each database dialect, and show the explanation in the GUI once a dialect has been chosen. It's one of the first hurdles any new Hibernate Tools user faces, and having to experiment with no clear feedback on whether it's correct now or not is a bit steep.)

Hello:
i meet the same question, but when i do such modify, the question still hanppen. and my database is mysql too. below give my configuation, help me please, thanks much.
<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE hibernate-reverse-engineering
SYSTEM "http://hibernate.sourceforge.net/hibernate-reverse-engineering-3.0.dtd" >
<hibernate-reverse-engineering>
<schema-selection match-catalog="IREIS2" match-table="SB_.*" />

<type-mapping>
<sql-type jdbc-type="CHAR" hibernate-type="java.lang.String" />
<sql-type jdbc-type="BIGINT" length='20' hibernate-type="java.lang.Long" />
<sql-type jdbc-type="SMALLINT" hibernate-type="java.lang.Short" />
<sql-type jdbc-type="DECIMAL" hibernate-type="java.math.BigDecimal" />
<!--
<sql-type jdbc-type="DATETIME" hibernate-type="java.util.Date" />
-->
</type-mapping>
<table-filter match-name="AF_*" exclude="true"/>
<table
catalog="IREIS2"
name="SB_EQUIPMENT_FILE"
class="EquipmentFileDomain">
<primary-key>
<generator class="AUTO">
</generator>
<key-column name="EQUIPMENT_FILE_ID" property="keyword" />
</primary-key>
</table>

<table
catalog="IREIS2"
name="SB_CUSTOM_ANNEX"
class="CustomAnnex">
<primary-key>
<generator class="AUTO">
</generator>
<key-column name="ANNEX_ID" property="keyword" />
</primary-key>

<foreign-key constraint-name="FK_SB_C_ANNEX_SB_E_FILE"
foreign-table="SB_EQUIPMENT_FILE">
<column-ref local-column="EQUIPMENT_FILE_ID"
foreign-column="EQUIPMENT_FILE_ID" />
<many-to-one exclude="true" />
<set property="customAnneies" />
</foreign-key>
</table>
</hibernate-reverse-engineering>

o, my question is "hbm2java ignoring parts of reveng.xml", as titile.

the rules are very simple:

Hibernate tools uses hibernate.default_schema and hibernate.default_catalog to know what the default schema and catalog are.

and

schema and catalog are the terms used by jdbc and what they mean depend on the specific jdbc driver implemenation you are using.

so if you have problems with matching tables then it is most likely because you haven't set hibernate.default_schema or hibernate.default_catalog
OR/and that the jdbc drivers implementation is doing something funky with them.