XWiki 소스를 뒤적거리던 중 이상한 넘을 발견했다.
뭐하는 녀석인가 봤더니, 경량급 IoC 컨테이너 였다. 이름하야 Plexus!!
사전적의미는 신경계의 망 등을 의미한다고 한다. 음. 어쨌거나,
이걸 또 공부해야 하나 싶으면서도 자꾸 궁금해진다. 담에 한번 써볼까 싶다.
How does Plexus compare with Spring?
- Complex component life cycles are not supported in Spring.
- Spring configuration files are much longer than the one for Plexus.
- Spring is not using IoC for all dependecies of components.
- Missing notion of "Component identity"
- Component class loader isolation.
- In Plexus you don't have to repeat yourself.
뭐하는 녀석인가 봤더니, 경량급 IoC 컨테이너 였다. 이름하야 Plexus!!
사전적의미는 신경계의 망 등을 의미한다고 한다. 음. 어쨌거나,
이걸 또 공부해야 하나 싶으면서도 자꾸 궁금해진다. 담에 한번 써볼까 싶다.
While Plexus is similar to other inversion-of-control (IoC) or dependency injection frameworks such as the Spring Framework, it is a full-fledged container that supports many more features such as:
- Component lifecycles
- Component instantiation strategies
- Nested containers
- Component configuration
- Auto-wiring
- Component dependencies, and
- Various dependency injection techniques including constructor injection, setter injection, and private field injection.
How does Plexus compare with Spring?
- Complex component life cycles are not supported in Spring.- Spring configuration files are much longer than the one for Plexus.
- Spring is not using IoC for all dependecies of components.
- Missing notion of "Component identity"
- Component class loader isolation.
- In Plexus you don't have to repeat yourself.
