Notice bibliographique
Résumé
OSGi, which stands for Open Services Gateway Initiative, is a service platform which facilitates the organization of code into reusable components called bundles. A bundle can be thought of as a Java archive (JAR) file with extra metadata describing its name, version, services offered, and dependencies to other bundles, among other things. The visibility of packages outside of a bundle can also be specified via metadata, giving developers a powerful way of separating their code into API and non-API packages. OSGi is not a new technology; it is used as the foundation of many software projects, perhaps the best known of which is the open-source Eclipse platform and the countless adopter products that are built on top of it. A developer extends Eclipse by writing plug-ins that add new functionality to the base platform. A plug-in is an OSGi bundle, and in fact Eclipse itself consists entirely of bundles. A plug-in can declare its dependencies to bundles in the base platform and use the features and services provided therein. In this fashion, complex applications can be built in a modular way. Although Eclipse is an example of an application built on OSGi technology, it is not the type of OSGi applications that the Rational development team is writing tools for. The OSGi applications this workshop refers to are actually enterprise OSGi applications. In essence, enterprise OSGi applications combine OSGi technology with enterprise technologies specified by the Java Enterprise Edition (Java EE) platform. Rules for how these separate technologies should integrate and behave are described in the OSGi Service Platform Enterprise specifications. Enterprise OSGi applications are meant to be run within an application server container such as IBM's WebSphere Application Server (WAS), which supplies bundled versions of the Java EE APIs for an application's use. Support for OSGi in WAS is based on components developed in the Apache Aries incubator project. In addition to the base OSGi Service Platform Enterprise specifications IBM provides technologies that complement the packaging and sharing of OSGi bundle. To package bundles together into a single cohesive application IBM introduces the concept of an Enterprise Business Archive(EBA). An EBA contains a number bundles along with meta-data that describes the dependencies and interactions of the OSGi application. This EBA can then be easily deployed to WebSphere application server. For those that are familiar with J2EE an EBA is very similar to a J2EE Enterprise Archive(EAR) file. IBM also provides the notion of a composite bundle. This kind of bundle is not a complete application but an aggregate of a number of other bundles. This composite bundle can then be used directly in an OSGi application or shared between a number of OSGi applications. Many developers are looking for a technology that provides a service-oriented, component-based environment that offers standardized ways to manage the software lifecycle. The OSGi programming model gives them this capability. In order to aid these developers to fully utilize this OSGi programming model the Rational Application Developer product is available with a rich set of OSGi development tools.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction distillée sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,001 | 0,001 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,000 | 0,000 |
| Bibliométrie | 0,000 | 0,002 |
| Études des sciences et des technologies | 0,000 | 0,000 |
| Communication savante | 0,000 | 0,000 |
| Science ouverte | 0,002 | 0,001 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,000 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule tête enseignante, pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».