Several issues encountered by eclipse using hibernate tools Reverse Engineering Plugin

1, when you use the Hibernate tool to generate hibernate profiles, you may be prompted not to parse .... XML error

Cause: It is possible that the Hibernate project that is used is not too coordinated with the version of the tools in JBoss, the XML file constraints are uncoordinated, if the network is not good or otherwise, the constraint file may not be local, and cannot be read locally from the network, resulting in an unsuccessful parsing of the generated XML

Workaround: When the *.cfg.xml is finished, modify the constraint XML constraint DTD. General problems will be solved

　　　　　　

General automatic generation is this constraint http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd//replaced with the bottom of this constraint, can normally parse xmlhttp:// www.hibernate.org/dtd/hibernate-configuration-3.0.dtd//if it is not resolved after the replacement, download the constraint or copy it from someone else in the network, and connect to the XML locally.

2, reverse engineering, when generating a configuration file, usually fill in its default schema (schema), generally default to the user name, note that the Oracle database field is uppercase

Problem: Write lowercase or do not write, query database reverse engineering, will report null pointer exception, or return an empty database

Workaround: Write Default_schema in the correct format (this attribute will be reflected in the configuration file), do not need reverse engineering, the configuration file should not be added

　　

Several issues encountered by eclipse using hibernate tools Reverse Engineering Plugin