ServletContext (Interface)

  •  When we do deployment (manual), server will scan "webapps" folder and identifies the projects which is deployed. 
  • All the identified projects will be kept in Meta-space of server.
  • For every project which is deployed in 'Meta-space' automatically 'Servlet Context' object will be created. 
  • Context object can be accessed in the entire project, meaning in all the servlets of the project.
  • As this is the first object created after deployment. we can keep the database details like URL, username, password and we can retrieve when ever we required.  
  • For all the servlets in the project what ever the data is required, that data will be placed in the Servlet Context object. 
  • Servlet Context object will be destroyed when we undeployed the project.
  • We can keep parameter data and attribute data inside the Servlet Context object.
  • In web.xml, <context-params> will be placed under <web-app> because it will be accessible by all the servlets present in the project. 

Comments

Post a Comment

Popular posts from this blog

Master and Slave Architecture in Jenkins

If we use one machine for jenkins then the moment we run multiple jobs it may burden the machine/vm which can lead to system crash  To reduce burden on jenkins server/vm we can go with master - Slave configuration which could be used to reduce the burden on jenkins server/vm by distributing tasks/load. Jenkins Master vs Jenkins Slave The machine/server where jenkins tools is installed can be referred as master machine which is used to create jobs, schedule the jobs and mange the jobs  It will also distribute jobs executions into slave machines/servers Note : We can Run/execute jobs on jenkins Master machine too however it's not recommended Jenkins Slave:  It's a machine which is connected to jenkins master machine and execute the job/task assigned by master machine/server. Slave server/machine will receive tasks from master machine for the job execution.
Read more

Difference b/w java.util.Date and java.sql.Date

java.util.Date => It is a utility class to handles Date in our java program. => It represents both Date and Time java.sql.Date => It is designed class to handle Dates w.r.t DB operations => It represents only Date,but not Time. Note: In sql package      Time(C) represents only => Time value      TimeStamp(C) represents both => Date and Time value. Date and Time API: (Joda-Time API) Until Java 1.7 version the classes present in Java.util package to handle Date and Time (like Date, Calendar, TimeZone etc) are not up to the mark with respect to convenience and performance. To overcome this problem in the 1.8 version oracle people introduced Joda-Time API. This API developed by joda.org and available in Java in the form of "java.time" package. # program for to display System Date and time. import Java.time.*; public class DateTime { public static void main(String[] args) { LocalDate date = LocalDate.now(); System.out.println(date); LocalTime t...
Read more

Ways to create a thread and which one is more scalable

 There are 2 ways to create a thread. i) Extending the thread class: ii) Implementing the Runnable interface. As java doesn't support multiple inheritance, So when a class extends Thread class, it cannot extend any other class but when a class implements Runnable interface it can also extend other classes as well. So, Implementing Runnable interface is more Scalable.
Read more