Hi Everybody, I need answers for these questions immediately. 1.What in your opinion are the three most crucial risks of developing on a J2EE application server that is the not the same as in production? Feel free to use specific examples of technologies, and different issues as they may arise in the Software Development Lifecycle. The issues that we are looking for may differ depending on what stage of the lifecycle the project is in. Cite specific examples (if any) from your experience, related to JBoss, BEA WebLogic, IBM Websphere Application Server. 2.What are the most commonly used design patterns used in a custom development application? Specifically, speak to applications that may have interfaces to different applications. Considerations would be a clean design such that other interfaces could be added with minimum code changes to the core modules? State specific design patterns that you have used to handle such situations. 3.Why would one use a singleton pattern instead of a class with static methods to ensure efficient memory usage? 4.What are the most common strategies used in Java to do transaction management where EJB�s are not being leveraged? For e.g. what kind of multi-threading issues would one have to take care off in the data access layer of an application where there is a possibility of a user creating or modifying the same entry simultaneously? Cite specific examples from experience if necessary. 5.Cite specific project experiences you have built XML DTDs and Schemas to map data in database schemas into XML format? Cite specific project experiences where you developed scripts to load Data in and out of databases? What file formats have you used in such experiences? What considerations apply when going about designing a custom application / module which does intensive data processing? -- would be really appreciated. Regards, babu kumar.