Whats the difference between hibernate.properties and hibernate.cfg.xml?

Which is the preferred one if I include mapping files using configuration API?

The reason I am asking this question... In some of the articles that I am reading, hibernate.properties is being used and in some others hibernate.cfg.xml is being used.

They are equivalent, you can add mapping files to the cfg.xml though. This is nice if you don't want to add them to a Configuration object programatically.

So, basically hibernate.cfg.xml provides extra features when compared to hibernate.properties. Then, why not just deprecate hibernate.properties. From a beginners point of view, I think it adds up confusion to have two different files basically doing the same job.

OR is there any other specific reason for which hibernate.properties is still being used?

I am curious about this question, also.

Why do we need both?

Is hibernate.properties preferred for standalone apps?

Drew

It's optional. Really, don't complain about free features. If we remove it, 50% would scream NO, the other 50% YES.

It's not a complaint at all.

I was just trying to understand why both exist and if one is preferred over the other.

I just started using Hibernate, so I don't know the history behind this.

Drew

Chris, Thanks for the info and please do not think it as a complaint. I was just trying to understand.

I really respect you guyz for the hardwork you do with the open source and especially with Hibernate for the quick and useful responses you provide us.

You da best.

Well, the difference is that you MUST define mappings.