)What is Hibernate?
2)What is ORM?
3)What does an ORM solution comprises of?
4)What are the different levels of ORM quality?
5)What is a pure relational ORM?
6)What is a meant by light object mapping?
7)What is a meant by medium object mapping?
8)What is meant by full object mapping?
9)What are the benefits of ORM and Hibernate?
10)How does hibernate code looks like?
11)What is a hibernate xml mapping document and how does it look like?
12)Show Hibernate overview?
13)What the Core interfaces are of hibernate framework?
14)What are Callback interfaces?
15)What are Extension interfaces?
16)What are the Extension interfaces that are there in hibernate?
17)What are different environments to configure hibernate?
18)What is the file extension you use for hibernate mapping file?
19)What do you create a SessionFactory?
20)What is meant by Method chaining?
21)What does hibernate.properties file consist of?
22)What should SessionFactory be placed so that it can be easily accessed?
23)What are POJOs?
24)What is object/relational mapping metadata?
25)What is HQL?
26)What are the different types of property and class mappings?
27)What is Attribute Oriented Programming?
28)What are the different methods of identifying an object?
29)What are the different approaches to represent an inheritance hierarchy?
30)What are managed associations and hibernate associations?
When is it better to use Hibernate versus EJB or JDBC? Are there times
we would use JDBC or EJB, and not Hibernate?
I know Hibernate models the architecture of EJB 3.0. What I have
discovered so far is
Advantages of Hibernate over EJB and/or JDBC
==================================
* Entity Beans have to follow naming conventions, POJOs can be any Java
object at all in Hibernate.
* Less code in Hibernate than JDBC
* CMP Entity Beans require a one-to-one mapping to database tables.
* EJB are (by reputation at least) slow.
* Someone has to determine which bean field maps to which table column
in EJB.
* EJB require special method names. If these are not followed
correctly, they will fail silently.
* Entity Beans have to reside within a J2EE application server
environment-they are a heavyweight solution.
* EJB cannot readily be extracted as "general purpose" components for
other applications.
* EJB can't be serializable.
* EJB rarely exist as portable components to be dropped into a foreign
application-you generally have to roll your own EJB solution.
Any links to tutorial, white paper, etc is welcomed.
2)What is ORM?
3)What does an ORM solution comprises of?
4)What are the different levels of ORM quality?
5)What is a pure relational ORM?
6)What is a meant by light object mapping?
7)What is a meant by medium object mapping?
8)What is meant by full object mapping?
9)What are the benefits of ORM and Hibernate?
10)How does hibernate code looks like?
11)What is a hibernate xml mapping document and how does it look like?
12)Show Hibernate overview?
13)What the Core interfaces are of hibernate framework?
14)What are Callback interfaces?
15)What are Extension interfaces?
16)What are the Extension interfaces that are there in hibernate?
17)What are different environments to configure hibernate?
18)What is the file extension you use for hibernate mapping file?
19)What do you create a SessionFactory?
20)What is meant by Method chaining?
21)What does hibernate.properties file consist of?
22)What should SessionFactory be placed so that it can be easily accessed?
23)What are POJOs?
24)What is object/relational mapping metadata?
25)What is HQL?
26)What are the different types of property and class mappings?
27)What is Attribute Oriented Programming?
28)What are the different methods of identifying an object?
29)What are the different approaches to represent an inheritance hierarchy?
30)What are managed associations and hibernate associations?
When is it better to use Hibernate versus EJB or JDBC? Are there times
we would use JDBC or EJB, and not Hibernate?
I know Hibernate models the architecture of EJB 3.0. What I have
discovered so far is
Advantages of Hibernate over EJB and/or JDBC
==================================
* Entity Beans have to follow naming conventions, POJOs can be any Java
object at all in Hibernate.
* Less code in Hibernate than JDBC
* CMP Entity Beans require a one-to-one mapping to database tables.
* EJB are (by reputation at least) slow.
* Someone has to determine which bean field maps to which table column
in EJB.
* EJB require special method names. If these are not followed
correctly, they will fail silently.
* Entity Beans have to reside within a J2EE application server
environment-they are a heavyweight solution.
* EJB cannot readily be extracted as "general purpose" components for
other applications.
* EJB can't be serializable.
* EJB rarely exist as portable components to be dropped into a foreign
application-you generally have to roll your own EJB solution.
Any links to tutorial, white paper, etc is welcomed.
No comments:
Post a Comment