Win a copy of Terraform in Action this week in the Cloud forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Al Hobbs
  • salvin francis

Spring core container is the basis for complete Spring framework?

 
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
All websites states that Spring core container is the basis for complete Spring framework i.e it is used across
the all modules like AOP,JDBC module,Web module etc.
As per my understading Spring core container main purpose is
to inject dependency which avoid the need of factory classes and methods. Is that correct?

Second question is when it is said, Spring core container is the basis for complete Spring framework .Say we take the
example of Spring AOP. As per understanding In Spring AOP , Getting the object of classes like
ProxyFactoryBean is achieved by core container. Right?

Thirdly, it is stated that Spring core container avoid the need of programming the singleton. How come singleton
classes are avoided by core container?
 
ranger
Posts: 17346
11
Mac IntelliJ IDE Spring
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes, the whole configuration and dependency is the base/skeleton/foundation for everything that Spring can do. Without Spring knowing about your classes, instantiating your classes, setting up the dependencies, then Spring wouldn't be able to add cool functionality to your application.

I am not sure what your understanding is based on your questions. Basically, I am not sure what you mean.

In terms of Singleton, there is the design pattern and there is scope. In Spring terms the Singleton scope, which is the default, means that Spring will only instantiate one instance of your object. And make sure it does not create another instance. The Singleton design pattern is different. It has the same basic results in terms of only one instance created. But in the Singleton design pattern, the class has code/functionality to enforce the single instance.

Mark
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic