We are using the eclipse "artifact generation" plugin to generate the hbm from an existing Oracle 9i database.

The trouble is, the schema name (the same as the user name in Oracle) in the resulting mapping files is set to the actual schema name of the database we are reverse engineering. This name seems to override the default_schema set in hibernate.cfg.xml at runtime.

This is a pain in that we may have multiple applications deployed against multiple schemas, for example a prod, test and training schema.

We have found a workaround. We do a global removal of the schema entry in each of the mapping files. Hibernate then seems to use default_schema. However we are uncomfortable in having to add that extra removal step.

Is there a better way to automate the removal? (custom templates?)

Is there a better way full stop? (are we missing something?)

Thanks in advance

Pat

create a patch to the .vm templates so we dont insert schema/catalog name if they are == to the defaults. and then add that to jira