StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2659597
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-04-17T19:00:16.413
FavoriteCount
0
LastActivityDate
2010-04-17T19:00:16.413
LastEditDate
LastEditorUserId
0
OwnerUserId
138830
ParentId
1276082
PostTypeId
2
Score
23
ViewCount
0
LastEditorDisplayName
text
Body
The problem can be state more generically: <blockquote> "According to the servlets (2.3) specification, the servlets are instantiated by the servlet engine by invoking the no-arg constructor. How can I initialize a servlet properly given that correct initialization depends on the central/global/unique/application configuration?" </blockquote> Actually, you can use serlvets with constructor and/or initialize them as you like. However, it requires a little bit of plumbing. Assuming you have a servlet with a constructor having arguments: <pre><code>package org.gawi.example.servlets; import java.io.*; import javax.servlet.*; import javax.servlet.http.*; public class SampleServlet extends HttpServlet { private final String mMessage; public SampleServlet(String message) { mMessage = message; } protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { response.setContentType("text/plain"); response.getWriter().write(mMessage); } } </code></pre> The first thing you need is a unique servlet whithin your application, let's call it InitializationServlet, to create all the required instances. Those instances must then be exported in the servlet context to be retrieve by another servlet (explained later). The InitializationServlet may look like this: <pre><code>package org.gawi.example.servlets; import javax.servlet.*; import javax.servlet.http.*; public class InitializationServlet extends HttpServlet { public void init() throws ServletException { SampleServlet servletA = new SampleServlet("this is servlet A"); SampleServlet servletB = new SampleServlet("this is servlet B"); SampleServlet servletC = new SampleServlet("this is servlet C"); getServletContext().setAttribute("servletA", servletA); getServletContext().setAttribute("servletB", servletB); getServletContext().setAttribute("servletC", servletC); } } </code></pre> You see that only the <code>init()</code> method has been provided. This servlet is not servicing any HTTP request. Its only purpose is to store the servlet in the ServletContext. Note that you could have also use this servlet to load your application configuration. So this can act as the web-application entry point, like the <code>main(String[] args)</code> method of a program. This might remind you of the ContextLoaderServlet of SpringSource. The last piece is the DelegateServlet that will effectively be instantiated by the servlet container, only this servlet will forward all the pertinent method calls to the wrapped servlet instance: <pre><code>package org.gawi.example.servlets; import java.io.*; import javax.servlet.*; import javax.servlet.http.*; public class DelegateHttpServlet extends HttpServlet { private static final String SERVLET_CONTEXT_KEY_INIT_PARAMETER = "servletContextKey"; private HttpServlet mServlet; public void init(ServletConfig servletConfig) throws ServletException { super.init(servletConfig); locateServlet(servletConfig); mServlet.init(servletConfig); } private void locateServlet(ServletConfig servletConfig) throws ServletException { String servletContextAttributeName = servletConfig.getInitParameter(SERVLET_CONTEXT_KEY_INIT_PARAMETER); if (servletContextAttributeName == null) { throw new ServletException("Unable to find init parameter '" + SERVLET_CONTEXT_KEY_INIT_PARAMETER + "'"); } Object object = servletConfig.getServletContext().getAttribute(servletContextAttributeName); if (object == null) { throw new ServletException("Unable to find " + servletContextAttributeName + " in servlet context."); } if (!(object instanceof HttpServlet)) { throw new ServletException("Object is not an instance of" + HttpServlet.class.getName() + ". Class is " + object.getClass().getName() + "."); } mServlet = (HttpServlet) object; } public void destroy() { mServlet.destroy(); } public void service(ServletRequest req, ServletResponse res) throws ServletException, IOException { mServlet.service(req, res); } } </code></pre> During its initialization, the DelegateServlet will look-up the target servlet in the servlet context using the <code>servletContextKey</code> servlet initial argument. The web.xml for such an application might look like that: <pre><code><?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd"> <web-app> <display-name>Example</display-name> <description>Example web showing handling of servlets w/ constructors.</description> <servlet> <servlet-name>Initialization</servlet-name> <servlet-class>org.gawi.example.servlets.InitializationServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet> <servlet-name>A</servlet-name> <servlet-class>org.gawi.example.servlets.DelegateHttpServlet</servlet-class> <init-param> <param-name>servletContextKey</param-name> <param-value>servletA</param-value> </init-param> <load-on-startup>2</load-on-startup> </servlet> <servlet> <servlet-name>B</servlet-name> <servlet-class>org.gawi.example.servlets.DelegateHttpServlet</servlet-class> <init-param> <param-name>servletContextKey</param-name> <param-value>servletB</param-value> </init-param> <load-on-startup>3</load-on-startup> </servlet> <servlet> <servlet-name>C</servlet-name> <servlet-class>org.gawi.example.servlets.DelegateHttpServlet</servlet-class> <init-param> <param-name>servletContextKey</param-name> <param-value>servletC</param-value> </init-param> <load-on-startup>4</load-on-startup> </servlet> <servlet-mapping> <servlet-name>A</servlet-name> <url-pattern>/servlet/a</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>B</servlet-name> <url-pattern>/servlet/b</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>C</servlet-name> <url-pattern>/servlet/c</url-pattern> </servlet-mapping> <session-config> <session-timeout>5</session-timeout> </session-config> </web-app> </code></pre> Be sure to load the InitializationServlet first, using a low <code><load-on-startup></code> value. The benefit of this approach is that <code>HttpServlet</code> objects can be handled like any other regular Java object or bean. Hence, it provides a better control over initialization: no more tricky stuff to do in the <code>init()</code> method, nor messy servlet init-arg handling.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to initialize a Servlet during startup with parameters?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USgawi
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.