I have a table called, for example, BANK_ATS. When I used Middlegen (r3) to generate this table, it names my hbm.xml file BankAt.hbm.xml and then hbm2java creates the java file as BankAt.java. I am not specifying specific tables, just letting Middlegen generate every table in my schema. Any suggestions why this might be happening and what I might do to fix it?

Thanks,
-Kat

Oops, I meant to say I use Middlegen to generate my mapping files from my already existing database. The BANK_ATS table exists in that database.

-K

I believe that behaviour is intended - Middlegen/Hibernate is assuming that the table name is plural, so when it builds the object, it uses the singular.

However, there are problems when it misinterprets the plural -- e.g. It takes the table SERVICE_TYPES and turns it into ServiceTyp.


Maury...

As correctly stated Middlegen changes (what it thinks is) plural to singular. This is a core feature of Middlegen thus changing it is difficult. Hence, I have start on, and am planning to finished the ability to define your own class names and/or property names using the plugin. The GUI is done but as you would be aware you cannot edit the name. This will be enabled. I have this on my list for release 4.

Hmm... I am not sure why if the table name is plural that the 's' shouldn't just be left alone. Sort of like how MSWord auto-capitalizes my words when I want it to just take my input as I type it in.

Oh well, I guess I still get to edit by hand for a while. But thanks for fixing that composite foreign key issue!

-Kat

No problem. This one is a middlegen core issue. As I said I will work around it in the plugin in r4.

I would guess that the thinking around that is:

Since a java class represents a single object, Middlegen makes the name singular (e.g. a class represents an instance of a single Service Type). The database table contains many instances of the that object, so it is plural (e.g. many Service Types).


Maury...

Yes - Thats how I work (this was the case before Middlegen as well). It is logical but does not universally apply. People are people - being different makes people and life interesting.

We just renamed the table, btw. Since we are still in dev stages, it wasn't that difficult. The table in question was an abbreviation of a phrase that ended in "service" and not a plural. We just added another word to the table name and now it doesn't think that abbreviation is plural. Like David said, people are people... luckily we are adaptable as well as different and interesting. :)

-Kat

:-)