<div>
You are getting confused between init params that you define on a single servlet through web.xml and context params that are defined for the whole web application context.<br />
<br />
init params are used by servlets to initialise themselves in the init() method.<br />
<br />
Context params are used to set parameters on the entire web application so any servlet can access them.
</div>


You are getting confused between init params that you define on a single servlet through web.xml and context params that are defined for the whole web application context.

init params are used by servlets to initialise themselves in the init() method.

Context params are used to set parameters on the entire web application so any servlet can access them.

<div>
What are practically examples where we use both?
</div>


What are practically examples where we use both?

<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
I am reading below link on servlets.<br />
<br />
<a href="http://tutorials.jenkov.com/java-servlets/web-xml.html" rel="ugc">http://tutorials.jenkov.com/java-servlets/web-xml.html</a><br />
<br />
Waht are the cases or scenarios we need to pass init-param, context params to a servlet. I am not clear on that concept which was being used even in spring framework also. <br />
How to know if to pass single servlet or to all servlets?<br />
Please advise
</div>
</div>


Hi,

I am reading below link on servlets.

http://tutorials.jenkov.com/java-servlets/web-xml.html

Waht are the cases or scenarios we need to pass init-param, context params to a servlet. I am not clear on that concept which was being used even in spring framework also. 
How to know if to pass single servlet or to all servlets?
Please advise

servlet init param and contect param

JavaServer Pages (JSP) allow the development of dynamically generated web pages. It uses the Java programming language; JSP pages are translated into servlets at runtime, with each servlet being cached and reused until the JSP is modified. JSP allows Java code to be interleaved with static web markup content, so the resulting page can be compiled and executed on the server to deliver the content.

Java Enterprise Edition (Java EE) is a specification defining a collection of Java-based server and client technologies and how they interoperate. Java EE specifies server and client architectures and uses profiles to define technology sets targeted at specific classes of applications. All Java EE profiles share a set of common features, such as naming and resource injection, packaging rules and security requirements.

Java EE

Java is a platform-independent, object-oriented programming language and run-time environment, designed to have as few implementation dependencies as possible such that developers can write one set of code across all platforms using libraries. Most devices will not run Java natively, and require a run-time component to be installed in order to execute a Java program.

Java

Programming includes both the specifics of the language you’re using, like Visual Basic, .NET, Java and others, but also the best practices in user experience and interfaces and the management of projects, version control and development. Other programming topics are related to web and cloud development and system and hardware programming.