Hi

my problem is simple but urgent

can anyone guide me or provide me some material on following topics









1
2
3

Nasir,

Here some thoughts:
1.
This depends of you approach of how you are gonna use Hibernate.
If you will use a layered architecture (see also http://www.hibernate.org/124.html) than you will use Hibernate just as you use any ordinary API. In you service/business layer you have to take care of transactions etc.
But if you want to automatically open en close connections (when needed!) for each request than you will have a complete different things to think of!

2.
I don't understand what you mean. Why not using Hibernate to select/retrieve the data? Why use more than 1 technique? You will just make you project more complex.
On the other hand * if you want to* you can use any technique available to retrieve data from a database.

3.
If you have a good design this will make if more easy to set up the mappings and configuration. In other words: if you have a good design which states exactly what you want to do, and you have experience with mappings and configurations these tasks should take less time then the design itself.

1. I'm using this structure and all I've seen so far is benefits. You see, struts means to separate layers, or concerns. Still, if you don't pay attention to what you're writing, you could destroy it. Hibernate helps you not to. It makes it easier to manipulate your model simply and separately. Using pure JDBC could confuse us and be a problem.

2. I agree with what marcelo said. Why use another technique? You would be looking for problems. The best thing to do is define a technique and use it all over.

3. I'd say design+mapping. You have to know a little bit of OO design before you use it, or you're lost.