Preethi,
Peter has explained it well. Thanks Peter. Since I already composed this post, didn't want to waste. So here is some add-ons.
1)why are parameters printed in a different sequence?
Inside the servlet engine init params are kept as HashTables. So when we take an Enumeration of keys/values, the order is not kept.
2) Why are other servlets (not involving init parameters)are running successfully even when i am not touching the already existing web.xml(no new <servlet> tag added neither a <servlet-mapping> tag)?
It is not a must that we should use web.xml for all our servlets. web.xml is just a holder file for runtime configuration params like init-param, which is startup-servlet etc. if we don't need to configure any params, then no need to edit web.xml. Our servlets will still work.
There is a standard (default) way , (which will always work) to map servlets.
http://yourhost/servlet/servletName Here "/servlet" is a 'magic' part which is directly mapped to .../WEB-INF/classes directory under our deployment dir. In other words, /servlet/ListManagerServlet means a ListManager.class which is under .../WEB-INF/classes/ dir.This is DEFAULT (work always) RULE used and specified in Servlet specifications. No other web.xml's URI/servlet-mapping necessary.
If we need extra decoration only, we need to edit web.xml. For example, you may have aservlet which could have been kept inside a very looooooong package like com.yourCompany.yourDept.yourProject.ListManagerServlet
If we apply the dafault rule ,we may have to invoke from browser like this.
http://localhost:8080/AppName/servlet/com.yourCompany.yourDept.yourProject.ListMa nagerServlet which is hard to type as well as difficult to remember. In these situations, we go for editing web.xml and do <servlet-mapping> work. Here we can specify whatever fancy URL we want for this above loooooong url and off you go!

3) The above code does not work if i omit giving a <servlet-name> tag or <servlet-mapping> i.e i tried it with just the init params in <servlet>(didn't work)??
Yes. It will not work. If at all we want to associate a set of init-params with a servlet we have to specify the URL also. Because /servlet/ListManagerServlet is used as mandatory rule and servlet engine directly calls the servlet under .../WEB-INF/classes dir.
If you want to send those params to /servlet/ListManagerServlet type URL then do this trick.

<servlet-mapping>
<servlet-name>
Test</servlet-name>
<url-pattern>/servlet/TestServlet</url-pattern>
</servlet-mapping>
4)where does the directory "servlets" under examples dir mapped for "servlet" in the path for any such servlet to be executed in case of tomcat??
There is no direct connection between servlets and the magic "/servlet" portion in URL. They are no way related. From Servlet 2.2 spec onwards the directory structure for a web abbplication is defined.
if you take any sample url
http://localhost:8080/MISApp/servlet/ListManagerServlet, this portion "/servlet/" is DIRECTLY mapped to ".../WEB-INF/classes/" directory under your webApplication deployment directory.
In "examples" web appln directory under Tomcat they just created a document directory named "servlets" to keep index of all example htmls. Nothing more than that. It could have beed renamed as "servletsList". In this case if you call
http://localhost:8080/examples/servletsList/index.html , the index.html will be invoked.
I am sure most of us would have got this doubt when started with servlets.

(Are "servlets" dir and "/servlet" URL portion anyway realted ?)
regds
maha anna
[This message has been edited by maha anna (edited May 13, 2001).]