Wells Fargo Java, J2ee Interview Questions

Interview Questions asked at Wells Fargo for Java / J2EE Position

Generally at Wells Fargo there will be multiple people interviewing you at the same moment.
Most of the times we have seen 5 to 6 people (includes manager, multiple technical guys).
And they asked questions from almost every area in J2EE.

• Firstly, they asked me to write a SQL query on board
• Then they asked me some design questions(design patterns)
• Also asked couple of questions in struts and Servlets.

Most of the time it was a discussion so can't remember few of the questions.
Anywz its very good and tough interview so prepare well technically and be kind, confident and never get into the pressure, because seeing 6 people in a room with a board is enough to make anybody nervous.
I would say that they generally look more into the right attitude rather than the right answers.

Below are couple of technical questions that they asked:

1. Drawbacks of struts framework
2. Spring versus Factory pattern
3. What is JDBC and explain JDBC architecture
4. Was asked to write a query which involved a join, group by clause, order by stuff
5. What is outer join
6. explain life cycle of Servlet
7. explain life cycle of Action servlet
8. What j2ee design patterns in used in a servlet?
9. some questions related to jdbc problems encountered in a j2ee application and a stand alone java swing application ? Not Sure what that means (not sure if I have framed the question correctly ) but it was some what like that...
10. What is a prototype in uml?
11. What happens when a request comes in how does the container handle it?
12. Version control tool CVS, basic commands
13. question related to exceptions in Java (do not recall entirely)
14. Difference between stateless & statefull session bean in ejb
15. again something on connection pooling do not remember exactly.
16. question related to hibernate configuration files
17. Difference between aggregation and composition
18. what are some of the exceptions related to string...
19. questions like... your skill sets, why should we hire you, refactoring approach, would you like to work old/new development... general questions, etc
20. What if you are added on a support project and consider if everyone goes on leave and clients reports a issue, how will you handle that?