PicoContainer釋出1.0 BETA版 (轉)
PicoContainer釋出1.0 BETA版 (轉)[@more@]PicoContainer是一個“微核心”(micro-kernel)的容器。它利用了Inversion of Control和Template Method模式,提供面向的開發、執行環境。從名字上就可以看出,PicoContainer是“極小”的容器,只提供了最基本的特性。其他容器可以在它的基礎上加入更多特性。因其小,PicoContainer也是剖析、研究的最佳。 ———————————— The PicoContainer team is proud to announce the release of the first beta of PicoContainer 1.0.
PicoContainer is an embeddable container for type-3 Inversion of Control (IoC) components. It is delivered as a set of abstractions, a couple of instantiable containers, a few adaptors for hierarchies and (optional) lifecycle management as well as support classes. We genuinely believe this to be the logical conclusion of the IoC component model.
Components:
The component model (igoring our lifecycle support) is unencumbered by obligations of . There is nothing to extend, nothing to implement and nothing to throw. The component model forces no obligations for meta-data on the developer or user of PicoContainer components. The design is so simple, that for very tightly coupled deployments, a developer could cherry pick components and embed them in their application without even importing let alone using anything from the org.picocontainer codebase.
Diversity:
From the abstractions, other container developers can build containers compatible and interoperable with PicoContainer. We encourage diversity of implementation as we are not building a single container. In terms of the PicoContainer deliverable, there are no external Jar dependancies, and no use of XML for component declarations. Along with the PicoContainer deliverable, there is a Technology Compatability Kit (TCK). This is in the foof the abstract JUnit test cases. A container developer can use this to ensure than their implementation of a PicoContainer is compatible with the design. Container developers may choose from-scratch designs, wrap of existing classes, or extending existing classes.
NanoContainer:
As a sister project to PicoContainer, we also have NanoContainer. Like PicoContainer, NanoContainer is more than one container. All are built to the PicoContainer design, and offer different embeddable visions. One interoperates with Nanning (the ect ) to prov aspect capability for arbitary components. Another retrofits JMX compatability to arbitary components. Some of the NanoContainers deliver component assembly and configuration via XML.
The Plan:
The plan is to build more containers and to sell the component design further.
- The PicoContainer team.
Visit
PicoContainer is an embeddable container for type-3 Inversion of Control (IoC) components. It is delivered as a set of abstractions, a couple of instantiable containers, a few adaptors for hierarchies and (optional) lifecycle management as well as support classes. We genuinely believe this to be the logical conclusion of the IoC component model.
Components:
The component model (igoring our lifecycle support) is unencumbered by obligations of . There is nothing to extend, nothing to implement and nothing to throw. The component model forces no obligations for meta-data on the developer or user of PicoContainer components. The design is so simple, that for very tightly coupled deployments, a developer could cherry pick components and embed them in their application without even importing let alone using anything from the org.picocontainer codebase.
Diversity:
From the abstractions, other container developers can build containers compatible and interoperable with PicoContainer. We encourage diversity of implementation as we are not building a single container. In terms of the PicoContainer deliverable, there are no external Jar dependancies, and no use of XML for component declarations. Along with the PicoContainer deliverable, there is a Technology Compatability Kit (TCK). This is in the foof the abstract JUnit test cases. A container developer can use this to ensure than their implementation of a PicoContainer is compatible with the design. Container developers may choose from-scratch designs, wrap of existing classes, or extending existing classes.
NanoContainer:
As a sister project to PicoContainer, we also have NanoContainer. Like PicoContainer, NanoContainer is more than one container. All are built to the PicoContainer design, and offer different embeddable visions. One interoperates with Nanning (the ect ) to prov aspect capability for arbitary components. Another retrofits JMX compatability to arbitary components. Some of the NanoContainers deliver component assembly and configuration via XML.
The Plan:
The plan is to build more containers and to sell the component design further.
- The PicoContainer team.
Visit
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/10752019/viewspace-982203/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 狀態管理神器 moox 釋出 1.0 beta版本
- 谷歌AngularJS釋出1.0版谷歌AngularJS
- 金山衛士1.0Beta釋出更小更快更安全
- Qt Creator 4.10 Beta版釋出QT
- GNOME 1.4 Beta 1釋出 (轉)
- Android 版的 VLC 釋出1.0正式版Android
- 谷歌Flutter1.0正式版釋出谷歌Flutter
- PHP框架Raxan1.0最終版釋出PHP框架
- Android Studio 1.0 正式版釋出!Android
- 釋出 umi 1.0 ???
- 新華LINUX釋出華鐳系統桌面版RAYS LX 1.5 Beta版(轉)Linux
- JuiceFS v1.0 beta3 釋出,支援 etcd、Amazon MemoryDB、Redis ClusterUIRedis
- React的替代方案Inferno釋出1.0版本React
- Fedora 31 Beta 釋出
- iOS9.3.3 Beta1開發者預覽版釋出iOS
- HertzBeat赫茲節拍 v1.0.beta.6 釋出,Linux監控來啦Linux
- UMind1.0釋出
- Google 釋出 ARCore 1.0Go
- AsteroidOS 1.0 釋出AST
- 騰訊 AlloyCrop 1.0 釋出
- Rust 1.0 正式釋出Rust
- iOS 10公測版beta2釋出 iOS 10公測版beta2怎麼樣?iOS
- 服務網格大事:Istio釋出1.0版本
- 正式釋出 Android 架構元件 1.0 穩定版Android架構元件
- PostgreSQL 12.0 Beta 釋出SQL
- Kotlin 1.3 正式釋出:Coroutine 『畢業』、Kotlin/Native 達成 1.0 Beta 等Kotlin
- 蘋果 macOS 12.2 開發者預覽版 Beta2 釋出蘋果Mac
- 蘋果釋出開發者預覽版iOS 8.3 beta 3系統蘋果iOS
- Fedora 24 Beta 版釋出下載!
- Griffon and Gradle 1.0釋出Gradle
- LaravelFlow工作流引擎1.0正式版釋出[附教程]Laravel
- 不和版本帝爭,16 年後 SciPy 1.0 版終釋出
- 彙編作業系統MenuetOS準備釋出1.0版作業系統
- Android 13 Beta 版釋出,諸多亮點不容錯過Android
- 蘋果 iOS/iPadOS 15.4 公測版 Beta 2 釋出蘋果iOSiPad
- iOS10.2.1 Beta公測版釋出 主要修復BugiOS
- Vue 3.0-beta.1 釋出!Vue
- HttpAsyncClient 4.1-beta1 釋出HTTPclient