5 ways of getting placed as 10 ways to be as java developer without knowing anything about development

1)if u hv time -take training from hyderabad ny gud crash course in ameerpet on sat & sun.

2)fill resume with words like jboss websphere weblogic rational rose design pattern and u dont need to know only dere version no nd 1 for each something

3)study mvc architecture nd say u had worked on struts spring and jsf nd also dere partner hibernate.

4)jboss drools can mkae u to US even.

5)in ur resume add lot of words to get easily in search on job portals.

6)put fake from any company from bangalore and show it .

7)while giving online test for companies always use screen capture recorder and record test so tat if you cant clear you can clear next time :)
8)when giving telephonic interview ask your friend who is really a developer to give interview in place of u.
9)!secret d interviewers r even nt good much technically thats why they take interview ,real coder hates taking interview if d company is very small no case works bcoz those companiess really works.

these all things work if you are exp...

jdbc vs hibernate

Many of the negatives you listed are no longer applicable with Hibernate and JPA:
* No configuration / mapping files needed - You can use annotations
* No need to write HQL Queries - there are some named Queries needed - many IDE automatically generate them
* Not complex - Classes generated by IDE like Netbeans

Reasons for using Hibernate:
* No or very little coding needed with Generic DAOs and Spring Hibernate Templates
* Clean object oriented design - even implement object oriented relationships
* Second level cache improves database performance
* Why reinventing the wheel?
* Works well with Spring
* Easier to maintain

You may avoid Hibernate if your database is having:
* Bad old legacy database design
* Too many stored procedures
* Relations between objects are complex

There may be 200 others who may come back and say that using an ORM is bad. This is one of the most debated items in many boards. But my 2c - to have fast turnarounds ORM is a must.
or

I think that it depends on the kind of task that you are going to solve.
Hibernate uses JDBC for executing queries.

Hibernate is really good if you have real-world entities that are represented in db as tables. You can manipulate by these entities, add/delete etc....Also it makes sense to use it in the big project to improve reusability, scalability and speed of development.

But you can get into trouble when you need to create some big complicated, aggregated report or you have non-standard queries that requires a lot of inner selects, joins that requires data from different tables. Usually such types of queries have performance constraints.
For this case you need to user JDBC or IBatis to have flexibility of buidling sql query.