Databases
StackOverflow2013
Postsdbo
POWhy destroy-method is giving error in Spring MVC?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy destroy-method is giving error in Spring MVC?
    primarykey
    data
    text
    <p>I have destroy method in my bean but it is not showing in the out put. Could you please help me here.</p> <pre><code>package com.vaannila; import org.springframework.context.ApplicationContext; import org.springframework.context.support.AbstractApplicationContext; import org.springframework.context.support.ClassPathXmlApplicationContext; public class HelloWorldApp { public static void main(String[] args) { AbstractApplicationContext context = new ClassPathXmlApplicationContext("beans.xml"); Ticket helloWorld = (Ticket) context.getBean("ticket"); helloWorld.setTicketNo("ABC009"); helloWorld.display(); context.close(); } } </code></pre> <p>below is my xml file</p> <pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"&gt; &lt;bean id="helloWorld" class="com.vaannila.HelloWorld"&gt; &lt;property name="message" value="Hello World!"&gt;&lt;/property&gt; &lt;/bean&gt; &lt;bean id="ticket" class="com.vaannila.Ticket" scope="prototype" init-method="init" destroy-method="destroy"/&gt; &lt;/beans&gt; </code></pre> <p>and Ticket class is below</p> <pre><code>package com.vaannila; public class Ticket { private String ticketNo=""; public String getTicketNo() { return ticketNo; } public void setTicketNo(String ticketNo) { this.ticketNo = ticketNo; } public void display() { System.out.println("Your Ticket No. is"+ ticketNo); } public void init() { System.out.println("Bean is ready You can use it now"); } public void destroy() { System.out.println("Bean is going to destroy"); } } </code></pre> <p>The out put is giving for init method but not for destroy method.. If i changed the init-method and destroy-method as default as below it is giving error in destroying the bean called "helloWorld"</p> <pre><code> &lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd" default-init-method="init" default-destroy-method="destroy"&gt; &lt;bean id="helloWorld" class="com.vaannila.HelloWorld"&gt; &lt;property name="message" value="Hello World!"&gt;&lt;/property&gt; &lt;/bean&gt; &lt;bean id="ticket" class="com.vaannila.Ticket" scope="prototype"/&gt; &lt;/beans&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USDhirendra Kumar
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. CONow i came to know that if bean is having prototype property in the bean definition then the destroy method is not calling. But why can anyone explain to me?
      singulars
      1. POWhy destroy-method is giving error in Spring MVC?
      1. USDhirendra Kumar
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload