Say, I have 100 beans used across the application. Every time i access the bean, it would parse the XML and create an object. This is how it works?
Ashwin Sridhar wrote: Its run-time when you handle stand-alone applications.
for the same 100 beans, it would create the objects after parsing the XML configurations on start up and have it somewhere (may be static) Is this is how it works?
Ashwin Sridhar wrote: you can have it loaded at server start up in case of web applications.
Actually I was more concerned about when the objects are getting "formed" as beans and stored(if only XML parsing is done once in the scope of application life time), the instantiation process no more different if it is done internally or in a traditional way.
Ashwin Sridhar wrote: Also you could make the beans instantiated at a time when these beans are needed.
Shankar Tanikella wrote:Thanks Mark, It is more informative. I shall continue reading. However, performance wise how is this Spring Framework.
All of the world's problems can be solved in a garden - Geoff Lawton. Tiny ad:
RavenDB is an Open Source NoSQL Database that’s fully transactional (ACID) across your databasehttps://coderanch.com/t/704633/RavenDB-Open-Source-NoSQL-Database