Reverse engineering a legacy database (Web host 4 life) F G B
Reverse engineering a legacy database
B This XML file has its own DTD for validation and autocompletion. C A table filter can exclude tables by name with a regular expression. However, in this example, you define a a default package for all classes produced for the tables matching the regular expression. D You can customize individual tables by name. The schema name is usually optional, but HSQLDB assigns the PUBLIC schema to all tables by default so this setting is needed to identify the table when the JDBC metadata is retrieved. You can also set a custom class name for the generated entity here. E The primary key column generates a property named id, the default would be messageId. You also explicitly declare which Hibernate identifier generator should be used. F An individual column can be excluded or, in this case, the name of the generated property can be specified the default would be messageText. G If the foreign key constraint FK_NEXT_MESSAGE is retrieved from JDBC metadata, a many-to-one association is created by default to the target entity of that class. By matching the foreign key constraint by name, you can specify whether an inverse collection (one-to-many) should also be generated (the example excludes this) and what the name of the many-to-one property should be. If you now run the Ant target with this customization, it generates a Message. hbm.xml file in the hello package in your source directory. (You need to copy the Freemarker and jTidy JAR files into your library directory first.) The customizations you made result in the same Hibernate mapping file you wrote earlier by hand, shown in listing 2.2. In addition to the XML mapping file, the Ant target also generates a Hibernate XML configuration file in the source directory:
Searching for affordable and reliable webhost to host and run your web applications? Go to our java web server services and you will be pleased.