Advertisement :
   Log In    OR    Register  
  Topics :  
RMI Example

Home >>> Spring Tutorials >>> Spring singleton >>> Spring Container Example
Struts Tutorials:
Struts2 Tag CheckBoxList
, Checkbox, Iterator, IF
Struts2 Tag Library Example Struts2 Tiles Example Struts2 Tiles I18N Example Struts2 Questions Struts Tiles I18N Example Struts Eclipse MVC Struts2 Tags Struts2 Example and Tutorial Struts MVC Struts2 Validation
Hibernate Tutorials: Hibernate Case Study Class Hierarchy Persist Example Using Hibernate Interceptor Hibernate Questions with Answer Hibernate Many-to-Many Mapping Example Hibernate one-to-many Mapping Example Hibernate and ORM tools Spring Hibernate Example Hibernate SessionFactory Example Hibernate Mapping Class Hierarchy Hibernate Questions Hibernate SessionFactory Questions Spring Hibernate Example: Spring Hibernate Case Study

Written By : Amit
Title :
Spring Remoting
Description : Java RMI Example
More...


Written By : ISHTEK
Title :
Spring Reflection
Description : POC Idea example code
More...


Written By : ISHTEK
Title :
Spring singleton
Description : Spring Container Example
More...


Written By : ISHTEK
Title :
Spring Features Updates News
Description : Bringing To Page
More...


Written By : ISHTEK
Title :
Spring Service
Description : Web Service Example
More...


Written By : ISHTEK
Title :
Spring WebService
Description : Example Code Discussed
More...

Tags/Keywords : Spring Singleton, Spring Container, Spring, Singleton,Questions, Example, Code, Tutorial, Article
Author : ISHTEK
Date (Year/Month/Date): 2009-09-25 Example showing Spring's singleton scope Bean Instance

Please be informed that NONE of the design/code from this
page is claiming to be some sort of best practices and we DO NOT expect
any of our visitor/reader of this page to assume this as some sort of
best practice for any context and should not be using this 
as it is without appropriate evaluation to their, so to say, 
specific programming context.

This page intends only to provide bit and piece of known ways  for
doing some sort of example and may not be fit for any other purpose.

Explaining difference between GOF Singleton pattern and SpringFramework Singleton pattern for the Bean. As we may be knowing that default scope for the bean from Spring container using Spring's ApplicationContext and BeanFactory is singleton. Thus we may have bean instance from the BeanFactory as singleton in nature, but is quite different from the GOF Singleton Pattern.
Advertisement :
As GOF Singleton Pattern looking at an instance that is per class and per classloader level. But SpringFramework Bean singleton scope is at per SpringFramework container level. So for a perticular Spring ApplicationContext and BeanFactory, there could be a single bean instance for a bean id. So to show this with the help of following example where I am first creating a single application context and BeanFactory using ClassPathXmlApplicationContext and passing test.xml configuration file as argument parameter. I am retrieving a Bean instance form the BeanFactory using a bean id and then setting value for the instance variable of this Bean instance. Then I am again retrieving another Bean instance for the second time but for the same bean id as that of bean id used in the first case. So if the Spring container manages singleton scope for this Bean, then I should expect the value set in this first case, to be retained in the second case as well.
import org.springframework.beans.factory.*;
import org.springframework.context.*;
import org.springframework.context.support.*;

public class Testclient{
  public Testclient() {
    try{
        ApplicationContext appContext = 
            new ClassPathXmlApplicationContext("test.xml");
        BeanFactory factory = appContext;
        //Retrieving bean from the bean factory.
        //Bean id as "one"
        One one1 = (One)factory.getBean("one");
        one1.setName("test name");

        //Bean id as "one"
        One one2 = (One)factory.getBean("one");
        System.out.println("Name from the singleton bean :"+one2.getName());
    } catch(Exception ex) {
        ex.printStackTrace();
    }
  }
  public static void main(String args[]) {
      new Testclient();
  }
}
The bold red color text above, shows the way Bean is retrieved from Spring container and the an example name value is set. While the bold blue colored text above, shows the way another bean instance is retrieved from Spring container, but using the same bean id. And the value from the second bean instance will be able to return the value that is already set in the earlier step. This shows that both these instances are the same, thus can be treated as singleton from Spring's singleton scope. This example is then slightly modified to include another instance of SpringFramework's ApplicationContext and BeanFactory instances again, and then the same ways , value for name field is set in first case, and then the value is retrieved from the another returned Bean instance from Spring Container. But now there is a difference, that is observed, and it is that the returned value is null, not the original value that is set in first case.
import org.springframework.beans.factory.*;
import org.springframework.context.*;
import org.springframework.context.support.*;

public class Testclient{
  public Testclient() {
    try{
        ApplicationContext appContext = 
            new ClassPathXmlApplicationContext("test.xml");
        BeanFactory factory = appContext;
        //Retrieving bean from the bean factory.
        One one1 = (One)factory.getBean("one");
        one1.setName("test name");

        ApplicationContext appContextNew = 
            new ClassPathXmlApplicationContext("test.xml");
        BeanFactory factoryNew = appContextNew;
        One one2 = (One)factoryNew.getBean("one");
        System.out.println("Name from the singleton bean :"+one2.getName());
    } catch(Exception ex) {
        ex.printStackTrace();
    }
  }
  public static void main(String args[]) {
      new Testclient();
  }
}
This shows that in the above modified code, we are dealing with two different Spring Context and so we have two different bean instances with one taking the setter value and the other returning null value. Code for the Bean in this example, is as follows:
public class One
{
  private String name;
  public void setName(String arg) {
	  name = arg;
  }
  public String getName() {
	  return name;
  }
}
and the Spring configuration file as follows:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" 
  "http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
  <bean id="one" class="One">
  </bean>
</beans>
Advertisement :
Please write your comments about this example, using below form.
Author of this article/writeup has expressed his/her willingness
to help or guide users with any technical difficulties he/she faces while working with the example code environment setting up, running and resolving any such exception raised during compile or at runtime. You may ask for any technical doubt or seek technical help related to this article by using following form to reach for technical help from the Author for FREE. This article's Author shall be reading your request and responding within reasonable time (no resolution timeframe defined as such).


	
Are you interested in solving a very interesting Technology Stack while Playing this Game          

Please write your Comment on this Matter
(This will be visible if found suitable):
Name: *
Email (will not be displayed): *
Matter: *
30,27
Enter bigger number from above :*
Home >>> Spring Tutorials >>> Spring singleton >>> Spring Container Example
Visitor/User referred related external URL:
(Visible upon review and approved by this site Administrator)
Referred By Name *:
Resource URL *: (e.g, URL should be starting with http://www.-----.---)
 
Resource Short Description *:
9,23
Enter bigger number from above : *

Please log in to add or reply to any matter<- requires login
Log in or Register
Copyright © 2008-2009, Interview-Questions-Tips-Forum, All Rights Reserved.
CONTACT    PRIVACY POLICY    DISCLAIMER
Terms of Use and Disclaimer :

This web site provides some of the information about various technologies, example 
code, tips, tutorials etc. Like any printed materials, content of these pages may 
become out of date over a period of time. Therefore all visitor/users of this web 
site are requested/advised to refer to the originating parties/sources for the 
latest changes and happenings for detailed information. This information is not 
intended to be a substitute for the original reference provided by the originating 
parties/sources.

By accessing and using this website in any ways, including, without
limitation, browsing the website pages, using any information, using any content and/or 
downloading any materials, you agree to and are bound by the terms of use 
described in this page and Usage Terms and Conditions. 
If you do not agree to all of 
the terms and conditions contained in the terms of use described in this
page and Usage Terms and Conditions, do not use this 
website in any manner. If you are using the website on behalf of your 
employer, you represent that you are authorized to accept these Terms of Use 
on your employer's behalf.

All Trademarks are property of their respective owner. Appropriate measure is being
taken for providing accurate and up-to-date information but like any printed materials,
these blog(s)/contents may eventually be outdated one day, so if you are using any 
of these information, please refer original content/documentation from respective sources. 
And under no circumstances shall the Author of these contents and/or this web site
be liable for any loss, damage, expense incurred or suffered which is claimed to have
occurred because of usage of the contents of this web site.
If you have any questions/queries/feedback/suggestions then please write to this web
site owner at contact.