 |  JFramework |  Web Search | Download | Newsletters | Firm Profile |
|
Menu What is a Framework Framework Objectives Developing a Framework Architecture J2EE App Architecture Physical Architecture App Building Approaches Structuring Web App Components Manager Object Relational Mapping Online Documentation Glossary News Download Message Board Contacts Summary
|
||
 |
 |  Components Manager |
| You Are Here: Home > Components Manager |
|
Architecture principles and overview The core of the interface between controller and model is the Components Manager. It controls business components creation, store, share and destruction. The reason for choosing this approach of business components management is based on performance considerations. Since creation and destruction of every business component is a very heavy operation in memory and processors cycles terms, the architecture based on containers of pre-created components is intended to overcome these problems. When the application is started Components Manager creates a set of business components containers. Each container stores business components of the same type. To create and destroy business components each container uses a Factory class instance. The Components Manager builds and initializes the containers. The containers build and store the business components. Components Manager uses an XML configuration file. The configuration file matches containers and factories. In case business components shortage in a container it is responsible to call the corresponding factory insobject for creation of missing component. |
|
|
|
||
