Please let me know the advantage of defining the class as static.Because while discussing about the perofrmance issue in our project,the manager has recommended to make the classes static whereever it is possible.
Is it really helps to improve performance? And at which context we have to make the class static?
In my new project they are using the servlet classes for all actions.That is no frameworks like struts,spring is used.They are using the servlet classes throught out the application.Say to add a user ,delete a user etc... for each action they are calling a separate servlet class. Is it the correct way to proceed ? Upto my knowledge the servlets can be used to load anything during the start up is the effective way.
If using servlets for all actions is not the proper way then please let me know how we can modify in the better way. Experts please help.
Instead of creating and opening new connections for each and every request we have the connections in a connection pool.But what happens when the number requests exceeds the pool size limit.Will any exception is thrown? If so then how we have to handle such situation.Please reply.
depends on the choices you make in your mappings - you mean my entity mappings(one to many,many to one etc..). In such a case also i have to create the hbm and pojo classes for all ,right ? So i think there is no way to reduce the number the hbm and pojo classes. Please correct me if i am wrong.
This is regarding hbm file creation in hibernate. In my database i am having 100 tables and i will be using all these tables for my querying.In such case do i need to create 100 hbm and pojo classes? or is there some other way to handle without creating hbm files for all the tables and only for few.Please clarify.
In struts if we are using the two struts-config.xml files then if you send or received any request or response then is it search for all the xml files?
Can we have any names for my struts configuration file say supri.xml or is it only struts-config.xml?