Hi, I am new to java and newer to hibernate. I am using exadel studio to generate some classes from database and it creates the folowing files to each class:

person.java
personDAO.java
persaoDAOImpl.java

Where do I write the business logic, so that I can acess other objects and have no problem with sessions.

Thanks

simple answer. persoaDAOIMPL.java

real answer. read up on the subject

I really don´t understand your point.

I answered your question. But, it's a pretty deep question that has quite a few different implementations. And the right implementation for you is best made by your decision after you read up on some hibernate practices and do some examples.

Ok, I readed some articles and each one has its own way to do this.
In my (dummy) opnion, I think that the person.java is the best way to put all business logic.

Looking at this point of view, I need to access the Session object from every class. To do this I think to create a super DAO class with a session instance.

you can't put your business logic in DAO , but you can put in new class using business delegate pattern, you can read how to utilize that pattern by googling.

This sound like a weak OOP implementation.

Any one look problems using this aproach?

personDAO.java (interface to access data)
personDAOImpl.java (implementation of access data)
person.java (gets/sets of columns and all business logic related with this object).

Thinking this way, I will have methods like:

myPerson.buy(product)
myPerson.cancel

instead of:
myShop.buy(myPerson, product)
myShop.cancel(myPerson)