Yo yo yo (cameltoe's never-ending yoyo)

Good night meme mode.

Servlet lifecycle [spoiler]This tutorial explains the Servlet interface and Servlet life cycle. A servlet example is given at the end which demonstrates the life cycle of a servlet. Servlets are managed components. They are managed by web container. Of the various responsibilities of web container, servlet life cycle management is the most important one. A servlet is managed through a well defined life cycle that defines how it is loaded, instantiated ad initialized, handles requests from clients and how it is taken out of service. The servlet life cycle methods are defined in the javax.servlet.Servlet interface of the Servlet API that all Servlets must implement directly or indirectly by extending GenericServlet or HttpServlet abstract classes. Most of the servlet you develop will implement it by extending HttpServlet class. The servlet life cycle methods defined in Servlet interface are init(), service() and destroy(). The life cycle starts when container instantiates the object of servlet class and calls the init() method, and ends with the container calling the destroy() method. The signature of this methods are shown below. public void init(ServletConfig config) throws ServletException<br /> public void service(ServletRequest req, ServletResponse res) throws ServletException, IOException<br /> public void destroy() The servlet life cycle consists of four steps, instantiation, initialization, request handling and end of service. Each of these steps is explained below. Loading and instantiation During this step, web container loads the servlet class and creates a new instance of the servlet. The container can create a servlet instance at container startup or it can delay it until the servlet is needed to service a request. Initialization During initialization stage of the Servlet life cycle, the web container initializes the servlet instance by calling the init() method. The container passes an object implementing the ServletConfig interface via the init() method. This configuration object allows the servlet to access name-value initialization parameters from the web application Understanding the Servlet life cycle with an example We will create a Servlet that will help you in better understanding the life cycle of a servlet. import java.io.IOException; import javax.servlet.ServletConfig; import javax.servlet.ServletException; import javax.servlet.http.HttpServlet; import javax.servlet.http.HttpServletRequest; import javax.servlet.http.HttpServletResponse; public class ServletLifeCycleExample extends HttpServlet { private int count; @Override public void init(ServletConfig config) throws ServletException { super.init(config); getServletContext().log("init() called"); count=0; } @Override protected void service(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { getServletContext().log("service() called"); count++; response.getWriter().write("Incrementig the count: Count = "+count); } @Override public void destroy() { getServletContext().log("destroy() called"); } } Above ServletLifeCycleExample Servlet extends HttpServlet and overrides init() Service() and destroy() methods. The servlet logs a message into server log file when servlet is initialized and sets counter to 0. Every time the service method is called, it increments the counter by 1 and displays the current value of counter to user. finally when destroy method is called, it logs a message to server log file. Compile above class and put it into WEB-INF/classes directory. Define the servlet and servlet mapping into web.xml file. If you do not know how to define the servlet in web.xml see this servlet example. Deploy the application and start the server. Call the servlet by opening the URL that you specified as url-pattern in web.xml. See the server log file. Hit the URL multiple times and you will see that a message is logged every time the service() method is called. The current value of counter will be displayed in browser.[/spoiler] Overloading and all that shit [spoiler]Method overriding is when a child class redefines the same method as a parent class, with the same parameters. For example, the standard Java class java.util.LinkedHashSet extends java.util.HashSet. The method add() is overridden in LinkedHashSet. If you have a variable that is of type HashSet, and you call its add() method, it will call the appropriate implementation of add(), based on whether it is a HashSet or a LinkedHashSet. This is called polymorphism. Method overloading is defining several methods in the same class, that accept different numbers and types of parameters. In this case, the actual method called is decided at compile-time, based on the number and types of arguments. For instance, the method System.out.println() is overloaded, so that you can pass ints as well as Strings, and it will call a different version of the method. Overriding is an example of run time polymorphism. The JVM does not know which version of method would be called until the type of reference will be passed to the reference variable. It is also called Dynamic Method Dispatch. Overloading is an example of compile time polymorphism. A Servlet is a Java class which conforms to the Java Servlet API, a protocol by which a Java class may respond to HTTP requests. Thus, a software developer may use a servlet to add dynamic content to a Web server using the Java platform. The generated content is commonly HTML, but may be other data such as XML. Servlets are the Java counterpart to non-Java dynamic Web content technologies such as CGI and ASP.NET. Servlets can maintain state in session variables across many server transactions by using HTTP cookies, or URL rewriting. The servlet API, contained in the Java package hierarchy javax.servlet, defines the expected interactions of a Web container and a servlet. A Web container is essentially the component of a Web server that interacts with the servlets. The Web container is responsible for managing the lifecycle of servlets, mapping a URL to a particular servlet and ensuring that the URL requester has the correct access rights. A Servlet is an object that receives a request and generates a response based on that request. The basic servlet package defines Java objects to represent servlet requests and responses, as well as objects to reflect the servlet's configuration parameters and execution environment. The package javax.servlet.http defines HTTP-specific subclasses of the generic servlet elements, including session management objects that track multiple requests and responses between the Web server and a client. Servlets may be packaged in a WAR file as a Web application. Servlets can be generated automatically by JavaServer Pages (JSP) compiler, or alternately use template engines such as WebMacro or Apache Velocity to generate HTML. Often servlets are used in conjunction with JSPs in a pattern called "Model 2", which is a flavor of the model-view-controller pattern.[/spoiler]

Bookmarked! http://talk.philmusic.com/board/index.php/topic,194781.msg2690639.html#msg2690639 http://talk.philmusic.com/board/index.php/topic,160424.0.html tangina nman tlga oh! kung kelan lalabas ung mga magagandang effex... un din ung time na ma-ubusan ng pang gatong! laki tlga damage ng laptop na to

Last edited by nanix84 (2010-07-22 06:14:14)

maganda pa ako sa gabi sa inyong lahat

here's it manang.. recording nung last gig namen http://www.fileden.com/files/2010/4/30/2845383//MOV03477.mp3

[spoiler][youtube]http://www.youtube.com/watch?v=MU-CHJu9FDg[/youtube][/spoiler]

^ows? [spoiler][youtube]http://www.youtube.com/watch?v=wGaR6wZOmmU[/youtube][/spoiler] [spoiler][youtube]http://www.youtube.com/watch?v=7_61tE7aTwU[/youtube][/spoiler]

.