Difference between revisions of "NCBO-OOR Server-Side Customization"
Jump to navigation
Jump to search
Benjamindai (talk | contribs) (Initial stubs for documentation.) |
Benjamindai (talk | contribs) |
||
| Line 1: | Line 1: | ||
=Introduction= | =Introduction= | ||
| − | - | + | The NCBO-OOR provides server-side flexibility by leveraging the enterprise pattern of "Dependency Injection." This is accomplished by applying the Spring technology which enables a partner to insert any software implementation that abides to the NCBO-defined interfaces purely by configuration. In other words, a different implementation can be deployed without a recompile or rebuild of the entire NCBO-OOR code-base. |
| − | - | + | |
| + | This first NCBO-OOR implemntation is based on the [[NCBO-OOR Architecture|BioPortal architecture]] and code-base. Thus, the majority of the developer considerations for NCBO-OOR is generally applicable to the BioPortal (and vice-versa). The author will note differences where appropriate. | ||
=BioPortal Pattern: Dependency Injection= | =BioPortal Pattern: Dependency Injection= | ||
Revision as of 14:48, 10 February 2009
Introduction
The NCBO-OOR provides server-side flexibility by leveraging the enterprise pattern of "Dependency Injection." This is accomplished by applying the Spring technology which enables a partner to insert any software implementation that abides to the NCBO-defined interfaces purely by configuration. In other words, a different implementation can be deployed without a recompile or rebuild of the entire NCBO-OOR code-base.
This first NCBO-OOR implemntation is based on the BioPortal architecture and code-base. Thus, the majority of the developer considerations for NCBO-OOR is generally applicable to the BioPortal (and vice-versa). The author will note differences where appropriate.