MétaCan
Menu
Retour à la cohorte
Enregistrement W180500109

Portlet development with spring portlet MVC and WebSphere portal V7

2011· article· en· W180500109 sur OpenAlexaff
Siamack Jabbarzadeh Farshi

Notice bibliographique

RevueConference of the Centre for Advanced Studies on Collaborative Research · 2011
Typearticle
Langueen
DomaineComputer Science
ThématiqueService-Oriented Architecture and Web Services
Établissements canadiensIBM (Canada)
Organismes subventionnairesnon disponible
Mots-clésComputer scienceWorld Wide WebScalabilityWeb pageEnterprise portalOperating system
DOInon disponible

Résumé

récupéré en direct d'OpenAlex

Motivation and Justification IBM WebSphere Portal is an industry leading Portal solution that is ranked as worldwide market share leader in the Portal products and user interaction tools enterprise software segment. Built upon enterprise-class WebSphere software, with added administrative and scalability features, It contains the widest range of portal technologies that help you develop and maintain first-class B2C, B2B and B2E portals and offers a complete set of portal services necessary to aggregate applications and content, such as: • Advanced usability features, as such drag & drop customizations and semantic tags that enable smart mark-ups and dynamic menus • Advanced tooling needed to build flexible, SOA-based solutions with unmatched scalability required by any size organization. • A click site management application featuring rollback and versioning capabilities to simplify moving portals from staging to production • A Page Builder that simplifies page creation, making it easy for business users to create pages and add content to pages • A site wizard that allows users to create and deploy independent virtual portals • A Template Page capability that speeds page creation by allowing portal pages to act as templates when creating other new portal pages • A Web application integrator that enables you to easily embed existing Web applications into your portals • Blog and Wiki capabilities supported via out-of-box content templates, making it easy to add popular social capabilities • Enhanced tagging and rating within the Page Builder theme, allowing users to easily organize and evaluate content without leaving the page they are viewing • Flexible access to existing enterprise data and applications, as well as to external news feeds or Web data • Unified user experience in which information and functions made available to each user can be customized based on the user or a role that the user has • Support for the Java Portlet 2.0 Standard and to the first Java Portlet Specification, the Java Portlet 1.0 Standard. • Support for Web Services for Remote Portlets (WSRP) 2.0 • Site layout support that enables you to incorporate existing static HTML, built with familiar HTML and PHP development tools, opening up the platform to additional content sources On the other hand, there is no doubt that Spring is the most complete lightweight Java/JEE container that is used widely in Java development software workshops. With a powerful dependency injection engine at its core and established software engineering practices such as interface-oriented design and Aspect oriented programming, Spring combines the enterprise application power with the simplicity of plain-old Java objects to bring about increased productivity and ease of testing. The Spring Portlet Model View Controller framework is a truly unique one compared to other frameworks because it is exclusively designed for developing portlets, leaving behind the limitation(s) that comes with providing portlet development support in an existing web framework. A web framework is based on servlet technology, which doesn't have a concept of lifecycle phases; therefore it ends up hiding the different lifecycle phases of a portlet. But, with Spring Portler Model View Controller framework you get a full featured Portlet Framework which preserves the lifecycle phases of Portlet With Data access being the requirement for most enterprise applications, Spring provides not only JDBC abstraction framework but also integration with Object Relational Mapping (ORM) Solutions such as Java Data Objects (JDO), Hibernate and Java Persistence API (JPA) on a variety of Platforms including WebSphere Application Server. With Transactions coupled tightly with Data access, Spring provides an abstract layer on top of different transactions management APIs both declaratively and programmatically. As an application developer, you can use Spring's transactions management facilities without having to know much out the underlying transaction management APIs. Combining two of the best solutions (WebSphere Portal and Spring), that are not only based on but also promote software engineering best practices, provides software practitioners with an exceptional opportunity to focus on the problem at hand and to have their development cycle reduced considerably.

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 enseignants

Ni 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.

score de la tête « metaresearch » (Codex)0,001
score de la tête « metaresearch » (Gemma)0,000
Version: codex-gemma-dda1882f352aStatut de validation: machine_predicted_unvalidated
Catégories candidatesaucune
Catégories consensuellesaucune
DomaineSignal candidat: aucune · Signal consensuel: aucune
Devis d'étudeSignal candidat: Expérimental (laboratoire) · Signal consensuel: aucune
GenreSignal candidat: Empirique · Signal consensuel: Empirique
Score de désaccord entre enseignants0,637
Score d'incertitude au seuil0,597

Scores Codex et Gemma par catégorie

CatégorieCodexGemma
Métarecherche0,0010,000
Méta-épidémiologie (sens strict)0,0000,000
Méta-épidémiologie (sens large)0,0000,000
Bibliométrie0,0000,001
Études des sciences et des technologies0,0010,000
Communication savante0,0000,000
Science ouverte0,0010,001
Intégrité de la recherche0,0000,000
Charge utile insuffisante (le modèle a refusé de juger)0,0000,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.

Tête enseignante Opus0,096
Tête enseignante GPT0,334
Écart entre enseignants0,238 · la distance entre les deux têtes enseignantes sur ce seul travail
Statut de validationscore_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écoule

Classification

machine, non validée

Prédiction automatique; un appel candidat d’une seule tête enseignante, pas un consensus.

Les modèles n’ont appliqué aucune catégorie : rien dans la taxonomie ne correspondait à ce travail.
Devis d'étudeExpérimental (laboratoire)
Domainenon disponible
GenreEmpirique

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 ».

En bref

Citations0
Publié2011
Routes d'admission1
Résumé présentoui

Explorer davantage

Même revueConference of the Centre for Advanced Studies on Collaborative ResearchMême sujetService-Oriented Architecture and Web ServicesTravaux en français237 207