Escuela Superior De Ingeniería

Total Page:16

File Type:pdf, Size:1020Kb

Escuela Superior De Ingeniería ESCUELA SUPERIOR DE INGENIERÍA INGENIERÍA TÉCNICA EN INFORMÁTICA DE GESTIÓN IMPLEMENTACIÓN DE EXTREMO A EXTREMO EN WS-BPEL 2.0 DE PROCESOS DE NEGOCIO INTERACTIVOS PARA GESTIÓN INMOBILIARIA María de los Ángeles Villalba Fernández 1 de julio de 2015 ESCUELA SUPERIOR DE INGENIERÍA INGENIERO TÉCNICO EN INFORMÁTICA DE GESTIÓN IMPLEMENTACIÓN DE EXTREMO A EXTREMO EN WS-BPEL 2.0 DE PROCESOS DE NEGOCIO INTERACTIVOS PARA GESTIÓN INMOBILIARIA Departamento: Ingeniería Informática Directores del proyecto: Antonia Estero Botaro y Antonio García Domínguez Autora del proyecto: María de los Ángeles Villalba Fernández Cádiz, 1 de julio de 2015 Fdo.: María de los Ángeles Villalba Fernández Agradecimientos Quisiera agradecer al grupo de investigación UCASE que haya confiado en mi para llevar a cabo este proyecto, y en especial, a mis tutores Antonia Estero Botaro y Antonio García Domínguez por tutorizar este proyecto, por todos los conocimientos y el tiempo que me han dedicado. A mi familia, sobre todo a mis padres y mis hermanos por apoyarme, por poder siempre contar con ellos y por darme fuerzas día tras día para continuar y no caer en la tentación de abandonar. Ellos han visto las horas de trabajo y el esfuerzo que le he dedicado a este proyecto. Por todo lo que me habéis ayudado y soportado, gracias. A mis amigos, sobre todo a los más íntimos, que han compartido conmigo este camino y han vivido todo ese esfuerzo dedicado, los que han estado en las malos y buenos momentos. Gracias por animarme a seguir adelante con el proyecto y confiar en mí. Por último, aunque no menos importante, a los familiares que ya no están entre nosotros, que confiaban en mí y me hubiera gustado que vieran como lo he conseguido. Índice general 1. Motivación y contexto 15 1.1. Introducción........................................... 15 1.2. Objetivos............................................ 16 1.3. Restricciones generales..................................... 17 1.4. Conceptos básicos........................................ 18 1.4.1. El lenguaje Java.................................... 18 1.4.2. El lenguaje WS-BPEL 2.0............................... 19 1.4.3. WSDL......................................... 23 1.4.4. SOAP.......................................... 24 1.4.5. XML Schema...................................... 26 1.4.6. XPath 2.0........................................ 27 1.4.7. BPMN 2.0....................................... 27 1.4.8. Maven.......................................... 35 1.4.9. BPELUnit........................................ 37 2. Planificación 41 2.1. Metodología........................................... 41 2.2. Fases del proyecto........................................ 41 2.2.1. Fase 0: Recopilación de la información........................ 41 2.2.2. Fase 1: Análisis y diseño del proyecto......................... 42 2.2.3. Fase 2: Aprendizaje de las tecnologías a utilizar.................... 42 2.2.4. Fase 3: Elección de herramienta gráfica para el desarrollo de composiciones..... 42 2.2.5. Fase 4: Desarrollo de la capa de persistencia, de dominio y los servicios web.... 43 2.2.6. Fase 5: Desarrollo de las composiciones WS-BPEL.................. 43 2.2.7. Fase 7: Pruebas..................................... 43 2.2.8. Fase 8: Documentación................................. 43 2.3. Distribución temporal...................................... 44 3. Análisis del proyecto 47 3.1. Introducción........................................... 47 3.2. Requisitos del sistema...................................... 47 3.2.1. Requisitos funcionales................................. 48 3.2.2. Requisitos no funcionales............................... 48 3.3. Modelo de análisis en UML.................................. 48 3.4. Modelado de casos de uso................................... 49 3.4.1. Diagrama de casos de uso............................... 49 3.4.2. Especificación de casos de uso............................. 49 3.5. Modelo conceptual de datos.................................. 58 3.6. Modelo de comportamiento del sistema............................ 59 3.6.1. Caso de uso: «Registrar cédula hipotecaria»...................... 61 3.6.2. Caso de uso: «Cambio de acreedor».......................... 64 3.6.3. Caso de uso: «Constitución de cédulas hipotecarias de registro»........... 67 7 4. Diseño del proyecto 71 4.1. Arquitectura del sistema.................................... 71 4.1.1. Arquitectura en capas.................................. 71 4.1.2. Arquitectura orientada a servicios........................... 76 4.2. Diseño de la base de datos................................... 79 4.2.1. Diseño conceptual................................... 79 4.2.2. Diseño lógico...................................... 99 5. Implementación de la capa de persistencia, de dominio y API 105 5.1. Implementación de la capa de persistencia y de dominio.................... 105 5.1.1. Hibernate........................................ 105 5.1.2. Java Persistence API.................................. 105 5.1.3. El principio DRY y el patrón GenericDAO...................... 106 5.1.4. El principio IOC y el framework Spring........................ 106 5.1.5. Inyección de Dependencia y Spring framework.................... 107 5.1.6. Programación orientada a aspectos........................... 108 5.1.7. Uso de anotaciones y principio de convención sobre configuración.......... 109 5.2. Implementación de los servicios web.............................. 113 5.2.1. Introducción a los servicios web............................ 113 5.2.2. Desarrollo de los servicios web............................ 114 5.2.3. Apache CXF...................................... 115 5.3. Seguridad en el sistema..................................... 116 6. Implementación de la capa de composiciones 117 6.1. Aprendizaje de nuevos conceptos................................ 117 6.1.1. XForms......................................... 117 6.1.2. XQuery 1.0....................................... 118 6.2. Detalles de implementación................................... 118 6.3. Composición «Registrar cédula hipotecaria».......................... 119 6.3.1. Función que realiza................................... 119 6.3.2. Participantes...................................... 119 6.3.3. Variantes........................................ 119 6.3.4. Formularios....................................... 119 6.3.5. Comportamiento de la composición.......................... 119 6.4. Composición «Cambio de acreedor».............................. 120 6.4.1. Función que realiza................................... 120 6.4.2. Participantes...................................... 124 6.4.3. Variantes........................................ 124 6.4.4. Formularios....................................... 125 6.4.5. Comportamiento de la composición.......................... 125 6.5. Composición «Constitución de cédulas hipotecarias de registro»............... 126 6.5.1. Función que realiza................................... 126 6.5.2. Participantes...................................... 126 6.5.3. Variantes........................................ 130 6.5.4. Formularios....................................... 130 6.5.5. Comportamiento de la composición.......................... 130 7. Pruebas 133 7.1. Introducción........................................... 133 7.2. El proceso de prueba...................................... 133 7.3. Técnicas de diseño de casos de prueba............................. 134 7.3.1. Enfoque estructural o de caja blanca.......................... 134 7.3.2. Enfoque funcional o de caja negra........................... 135 7.3.3. Enfoque aleatorio.................................... 135 7.4. Estrategia de aplicación de las pruebas............................. 135 7.4.1. Pruebas de unidad................................... 135 7.4.2. Pruebas de integración................................. 136 7.4.3. Pruebas del sistema................................... 136 7.4.4. Pruebas de aceptación................................. 137 7.5. Plan de pruebas......................................... 137 7.5.1. Qué se va a probar................................... 137 7.5.2. Cómo se va a probar.................................. 153 7.6. Ejecución de las pruebas.................................... 156 7.7. Detalles de las pruebas..................................... 160 8. Conclusiones 161 8.1. Objetivos alcanzados...................................... 161 8.2. Conclusiones personales.................................... 161 8.3. Trabajo futuro.......................................... 162 A. Manual de usuario 163 A.1. Uso para un Usuario...................................... 163 A.1.1. Entidad de crédito................................... 163 A.1.2. Entidad de crédito compradora............................. 168 A.1.3. Registro de la propiedad................................ 171 A.1.4. Notario......................................... 172 A.2. Uso para el Administrador del sistema............................. 173 A.3. Organización y asignación de tareas a recursos......................... 174 B. Manual del desarrollador 177 B.1. Instalación de herramientas................................... 177 B.1.1. Maven.......................................... 177 B.1.2. JDK de Java...................................... 177 B.1.3. Subversion....................................... 177 B.1.4. Eclipse JEE....................................... 178 B.1.5. TomEE +........................................ 178 B.1.6. Intalio|Designer..................................... 178 B.1.7. Servidor
Recommended publications
  • The State of the Feather
    The State of the Feather An Overview and Year In Review of The Apache Software Foundation The Overview • Not a replacement for “Behind the Scenes...” • To appreciate where we are - • Need to understand how we got here 2 In the beginning... • There was The Apache Group • But we needed a more formal and legal entity • Thus was born: The Apache Software Foundation (April/June 1999) • A non-profit, 501(c)3 Corporation • Governed by members - member based entity 3 “Hierarchies” Development Administrative PMC Members Committers Board Contributors Officers Patchers/Buggers Members Users 4 At the start • There were only 21 members • And 2 “projects”: httpd and Concom • All servers and services were donated 5 Today... • We have 227 members... • ~54 TLPs • ~25 Incubator podlings • Tons of committers (literally) 6 The only constant... • Has been Change (and Growth!) • Over the years, the ASF has adjusted to handle the increasing “administrative” aspects of the foundation • While remaining true to our goals and our beginnings 7 Handling growth • ASF dedicated to providing the infrastructure resources needed • Volunteers supplemented by contracted out SysAdmin • Paperwork handling supplemented by contracted out SecAssist • Accounting services as needed • Using pro-bono legal services 8 Staying true • Policy still firmly in the hands of the ASF • Use outsourced help where needed – Help volunteers, not replace them – Only for administrative efforts • Infrastructure itself is a service provided by the ASF • Board/Infra/etc exists so projects and people
    [Show full text]
  • Return of Organization Exempt from Income
    OMB No. 1545-0047 Return of Organization Exempt From Income Tax Form 990 Under section 501(c), 527, or 4947(a)(1) of the Internal Revenue Code (except black lung benefit trust or private foundation) Open to Public Department of the Treasury Internal Revenue Service The organization may have to use a copy of this return to satisfy state reporting requirements. Inspection A For the 2011 calendar year, or tax year beginning 5/1/2011 , and ending 4/30/2012 B Check if applicable: C Name of organization The Apache Software Foundation D Employer identification number Address change Doing Business As 47-0825376 Name change Number and street (or P.O. box if mail is not delivered to street address) Room/suite E Telephone number Initial return 1901 Munsey Drive (909) 374-9776 Terminated City or town, state or country, and ZIP + 4 Amended return Forest Hill MD 21050-2747 G Gross receipts $ 554,439 Application pending F Name and address of principal officer: H(a) Is this a group return for affiliates? Yes X No Jim Jagielski 1901 Munsey Drive, Forest Hill, MD 21050-2747 H(b) Are all affiliates included? Yes No I Tax-exempt status: X 501(c)(3) 501(c) ( ) (insert no.) 4947(a)(1) or 527 If "No," attach a list. (see instructions) J Website: http://www.apache.org/ H(c) Group exemption number K Form of organization: X Corporation Trust Association Other L Year of formation: 1999 M State of legal domicile: MD Part I Summary 1 Briefly describe the organization's mission or most significant activities: to provide open source software to the public that we sponsor free of charge 2 Check this box if the organization discontinued its operations or disposed of more than 25% of its net assets.
    [Show full text]
  • 7.1 Oracle Bpel Process Manager
    Institute of Architecture of Application Systems University of Stuttgart Universitätsstraße 38 D–70569 Stuttgart Diplomarbeit Nr. 2728 Fault Handling Across the Web Services Stack Pablo Fuentetaja Abad Course of Study: Computer Science Examiner: Prof. Dr. Frank Leymann Supervisor: Dipl.-Inf. Oliver Kopp Commenced: January ,14 2008 Completed: July, 15 2008 CR-Classification: C.2.0, C.2.1, C.2.2, C.2.4, D.2.11 Acknowledgments To my family and friends. Their support has helped me during the difficult moments. Without them this would have not been possible. To Prof. Dr. F. Leymann. For offer me the opportunity of developing this work in the Institut für Architektur von Anwendungssystemen. To Dipl.-Inf. O. Kopp. For his work, help, and supervision during these months. To Dipl.-Inf. Matthias Wieland. For his last supervision and comments. Abstract The Business Process Execution Language (BPEL) is an XML based language for describing business process behaviour based on Web services. The BPEL notation includes flow control, variables, concurrent execution, input and output, transaction scoping/compensation, and error handling. These processes are executed on a BPEL engine which calls and receives messages from external parties. The BPEL process is suspended or terminated if such communication fails, not providing any detailed information about the cause. The aim of this diploma thesis is the description of the different communication faults that can be found throughout the Web Services Stack, how they are reflected and describe a general concept of fault handling. Two BPEL engines are use on this thesis “Oracle BPEL Process Manager” and “Apache ODE”.
    [Show full text]
  • Performance Evaluation of Enterprise Service Buses Towards Support of Service Orchestration Themba Shezi, Edgar Jembere , and Mathew Adigun the Internet
    International Conference on Computer Engineering and Network Security (ICCENS'2012) December 26-27, 2012 Dubai (UAE) Performance Evaluation of Enterprise Service Buses towards Support of Service Orchestration Themba Shezi, Edgar Jembere, and Mathew Adigun the Internet. In most scenarios services are combined in a Abstract- The use of Enterprise Service Bus (ESB) as the process to achieve a business objective. For defining these cornerstone for system integrations has shown improvement in many processes Web Service Business Process Execution Language aspect of business information systems, including paving a way for (WS-BPEL) is used. Service Oriented computing, reusability, business to business collaboration and standard based communication infrastructure. ESB SOA implementations that were based on only endpoints as a concept defines set of capabilities which includes message fall short of the key infrastructure to support data routing, transformation, and service orchestration. However there transformation, event handling, and durable messaging. These exist different approaches towards achieving these capabilities. There additional requirements to SOA led to what is known as is much ongoing research on architectural issues and enabling Enterprise Service Bus (ESB) [3]. technologies for ESBs, but the body of knowledge regarding service ESB is a standard based integration infrastructure that automation and orchestration schemes needs some improvements. In this work we provide comparative performance evaluation of enables heterogeneous services and applications to interact by ServiceMix, Mule and JBoss ESB regarding service orchestration. combining web service technology, messaging, intelligent The results showed that the use of Apache ODE as the orchestration routing, data transformation and service orchestration [2]. The engine gave ServiceMix an advantage over the other ESBs.
    [Show full text]
  • Full-Graph-Limited-Mvn-Deps.Pdf
    org.jboss.cl.jboss-cl-2.0.9.GA org.jboss.cl.jboss-cl-parent-2.2.1.GA org.jboss.cl.jboss-classloader-N/A org.jboss.cl.jboss-classloading-vfs-N/A org.jboss.cl.jboss-classloading-N/A org.primefaces.extensions.master-pom-1.0.0 org.sonatype.mercury.mercury-mp3-1.0-alpha-1 org.primefaces.themes.overcast-${primefaces.theme.version} org.primefaces.themes.dark-hive-${primefaces.theme.version}org.primefaces.themes.humanity-${primefaces.theme.version}org.primefaces.themes.le-frog-${primefaces.theme.version} org.primefaces.themes.south-street-${primefaces.theme.version}org.primefaces.themes.sunny-${primefaces.theme.version}org.primefaces.themes.hot-sneaks-${primefaces.theme.version}org.primefaces.themes.cupertino-${primefaces.theme.version} org.primefaces.themes.trontastic-${primefaces.theme.version}org.primefaces.themes.excite-bike-${primefaces.theme.version} org.apache.maven.mercury.mercury-external-N/A org.primefaces.themes.redmond-${primefaces.theme.version}org.primefaces.themes.afterwork-${primefaces.theme.version}org.primefaces.themes.glass-x-${primefaces.theme.version}org.primefaces.themes.home-${primefaces.theme.version} org.primefaces.themes.black-tie-${primefaces.theme.version}org.primefaces.themes.eggplant-${primefaces.theme.version} org.apache.maven.mercury.mercury-repo-remote-m2-N/Aorg.apache.maven.mercury.mercury-md-sat-N/A org.primefaces.themes.ui-lightness-${primefaces.theme.version}org.primefaces.themes.midnight-${primefaces.theme.version}org.primefaces.themes.mint-choc-${primefaces.theme.version}org.primefaces.themes.afternoon-${primefaces.theme.version}org.primefaces.themes.dot-luv-${primefaces.theme.version}org.primefaces.themes.smoothness-${primefaces.theme.version}org.primefaces.themes.swanky-purse-${primefaces.theme.version}
    [Show full text]
  • Kuali Student Service System: Technical Architecture Phase 1 Recommendations
    Kuali Student Service System Technical Architecture Phase 1 Recommendations Kuali Student Service System Technical Architecture Phase 1 Recommendations December 31 2007 Kuali Student Technical Team Technical Architecture Phase 1 deliverables 2/14/2008 1 Kuali Student Service System Technical Architecture Phase 1 Recommendations Table of Contents 1 OVERVIEW ........................................................................................................................ 4 1.1 REASON FOR THE INVESTIGATION ................................................................................... 4 1.2 SCOPE OF THE INVESTIGATION ....................................................................................... 4 1.3 METHODOLOGY OF THE INVESTIGATION .......................................................................... 4 1.4 CONCLUSIONS ............................................................................................................... 5 1.5 DECISIONS THAT HAVE BEEN DELAYED ............................................................................ 6 2 STANDARDS ..................................................................................................................... 7 2.1 INTRODUCTION .............................................................................................................. 7 2.2 W3C STANDARDS .......................................................................................................... 7 2.3 OASIS STANDARDS ......................................................................................................
    [Show full text]
  • A Mediator Architecture for Context-Aware Composition in SOA
    A Mediator Architecture for Context-aware Composition in SOA Hicham Baidouri, Hatim Hafiddi, Mahmoud Nassar and Abdelaziz Kriouile IMS Team, SIME Laboratory, ENSIAS, Rabat, Morocco Keywords: Context, Ubiquitous Computing, Context-aware Service, Context-aware Composite Service, Aspect Paradigm, Context-Aware Composition, Model Driven Engineering. Abstract: The emergence of wireless technologies, intelligent mobile devices and service oriented architectures has enabled the development of the context-aware service oriented systems. This evolution has put the light on a challenging problem: how to dynamically compose services in SOA based systems to perform more complicated functionalities and provide richer user experience? As observed from the literature, several researches focus mainly on context-aware service design and modelling, but few studies have worked on the composition of this new kind of service to provide more complicated features. In this paper, we aim to present our proposal of adapting service composition by the integration of context during the composition process. This dynamic context-aware composition of services is realized through our Mediator Architecture for Context-Aware Composition (MACAC). 1 INTRODUCTION aware composition computing emphasizes more open-endedness in terms of analysis, design and Over the last few years, adaptive service implementation phases. composition has emerged as one of the most desired CACS development can profit from existing features that allow the integration and cooperation paradigms and technologies such as process between pre-existing services to bring out new orchestration language (e.g., BPEL (OASIS, 2007)) features. This process, known as contextual service and Model Driven Engineering (MDE (Favre, composition, requires from the composite services to 2004)).
    [Show full text]
  • Sc Collaborator: a Service Oriented Framework for Construction Supply Chain Collaboration and Monitoring
    SC COLLABORATOR: A SERVICE ORIENTED FRAMEWORK FOR CONSTRUCTION SUPPLY CHAIN COLLABORATION AND MONITORING A DISSERTATION SUBMITTED TO THE DEPARTMENT OF CIVIL AND ENVIRONMENTAL ENGINEERING AND THE COMMITTEE ON GRADUATE STUDIES OF STANFORD UNIVERSITY IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF DOCTOR OF PHILOSOPHY Chin Pang Cheng November 2009 © Copyright by Chin Pang Cheng 2009 All Rights Reserved ii I certify that I have read this dissertation and that, in my opinion, it is fully adequate in scope and quality as a dissertation for the degree of Doctor of Philosophy. ___________________________________ (Kincho H. Law) Principal Adviser I certify that I have read this dissertation and that, in my opinion, it is fully adequate in scope and quality as a dissertation for the degree of Doctor of Philosophy. ___________________________________ (Hans C. Bjornsson) I certify that I have read this dissertation and that, in my opinion, it is fully adequate in scope and quality as a dissertation for the degree of Doctor of Philosophy. ___________________________________ (John Haymaker) Approved for the University Committee on Graduate Studies. iii Abstract Importance of supply chain integration has been shown in many industry sectors. The construction industry is one of the least integrated among all major industries. One of the major reasons is that construction supply chains are unstable and often consist of numerous distributed members, most of which are small and medium construction companies. With the proliferation of the Internet and the current maturity of web services standards, service oriented architecture (SOA) with open source technologies is a desirable computing model to support construction supply chain integration and collaboration due to its flexibility and low cost.
    [Show full text]
  • Apache Buildr in Action a Short Intro
    Apache Buildr in Action A short intro BED 2012 Dr. Halil-Cem Gürsoy, adesso AG 29.03.12 About me ► Round about 12 Years in the IT, Development and Consulting ► Before that development in research (RNA secondary structures) ► Software Architect @ adesso AG, Dortmund ► Main focus on Java Enterprise (Spring, JEE) and integration projects > Build Management > Cloud > NoSQL / BigData ► Speaker and Author 29.03.12 2 Scala für Enterprise-Applikationen Agenda ► Why another Build System? ► A bit history ► Buildr catchwords ► Tasks ► Dependency management ► Testing ► Other languages ► Extending 3 Apache Buildr in Action – BED-Con 2012 Any aggressive Maven fanboys here? http://www.flickr.com/photos/bombardier/19428000/4 Apache Buildr in Action – BED-Con 2012 Collected quotes about Maven “Maven is such a pain in the ass” http://appwriter.com/what-if-maven-was-measured-cost-first-maven-project 5 Apache Buildr in Action – BED-Con 2012 Maven sucks... ► Convention over configuration > Inconsistent application of convention rules > High effort needed to configure ► Documentation > Which documentation? (ok, gets better) ► “Latest and greatest” plugins > Maven @now != Maven @yesterday > Not reproducible builds! ► Which Bugs are fixed in Maven 3? 6 Apache Buildr in Action – BED-Con 2012 Other buildsystems ► Ant > Still good and useful, can do everything... but XML ► Gradle > Groovy based > Easy extensible > Many plugins, supported by CI-Tools ► Simple Build Tool > In Scala for Scala (but does it for Java, too) 7 Apache Buildr in Action – BED-Con 2012 Apache
    [Show full text]
  • Programme and Challenge
    Deliverable D6.2: Adaptive Execution Infrastructure Version 1.0 – User Guide Date: Monday, 20. December 2010 Author(s): A. Tsalgatidou, G. Athanasopoulos, I. Pogkas, P. Kouki (NKUA) Dissemination level: PU WP: WP6 - Adaptive execution infrastructure Version: 1.0 Keywords: Execution Infrastructure, User Guide Description: Envision Adaptive Execution Infrastructure User Guide ICT for Environmental Services and Climate Change Adaption Small or Medium-scale Focused Research Project ENVISION (Environmental Services Infrastructure with Ontologies) Project No: 249120 Project Runtime: 01/2010 – 12/2012 Copyright ENVISION Consortium 2009-2012 Document metadata Quality assurors and contributors Quality François Tertre (BRGM), Iker Larizgoitia (UIBK) assuror(s) Contributor(s) Version history Version Date Description 0.1 5/10/2010 Initial TOC proposal. 0.2 4/11/2010 Preliminary Input. 0.3 23/11/2010 Draft version with input in most sections. 0.4 30/11/2010 1st completed internal version. 0.6 08/12/10 Version ready for internal review. Version updated according to internal review 0.7 16/12/10 comments. 0.9 20/12/10 Version approved by the technical coordinator. 1.0 22/12/2010 Version approved by the project coordinator. Copyright ENVISION Consortium 2009-2012 Page 2 / 23 Executive Summary A core component of Envision is the Execution Infrastructure, which according to the DoW [1] is responsible for supporting the execution of environmental service chains, their data-driven adaptation and the semantic-based mediation among the constituent services. These features constitute the operational core of Envision and will support the functionality of the Envision Portal. The goal of this deliverable is to - provide an overview of the features of the Envision Execution Infrastructure implemented in version 1.0 and - provide a user-guide with details on the installation and use of the Infrastructure.
    [Show full text]
  • Code Smell Prediction Employing Machine Learning Meets Emerging Java Language Constructs"
    Appendix to the paper "Code smell prediction employing machine learning meets emerging Java language constructs" Hanna Grodzicka, Michał Kawa, Zofia Łakomiak, Arkadiusz Ziobrowski, Lech Madeyski (B) The Appendix includes two tables containing the dataset used in the paper "Code smell prediction employing machine learning meets emerging Java lan- guage constructs". The first table contains information about 792 projects selected for R package reproducer [Madeyski and Kitchenham(2019)]. Projects were the base dataset for cre- ating the dataset used in the study (Table I). The second table contains information about 281 projects filtered by Java version from build tool Maven (Table II) which were directly used in the paper. TABLE I: Base projects used to create the new dataset # Orgasation Project name GitHub link Commit hash Build tool Java version 1 adobe aem-core-wcm- www.github.com/adobe/ 1d1f1d70844c9e07cd694f028e87f85d926aba94 other or lack of unknown components aem-core-wcm-components 2 adobe S3Mock www.github.com/adobe/ 5aa299c2b6d0f0fd00f8d03fda560502270afb82 MAVEN 8 S3Mock 3 alexa alexa-skills- www.github.com/alexa/ bf1e9ccc50d1f3f8408f887f70197ee288fd4bd9 MAVEN 8 kit-sdk-for- alexa-skills-kit-sdk- java for-java 4 alibaba ARouter www.github.com/alibaba/ 93b328569bbdbf75e4aa87f0ecf48c69600591b2 GRADLE unknown ARouter 5 alibaba atlas www.github.com/alibaba/ e8c7b3f1ff14b2a1df64321c6992b796cae7d732 GRADLE unknown atlas 6 alibaba canal www.github.com/alibaba/ 08167c95c767fd3c9879584c0230820a8476a7a7 MAVEN 7 canal 7 alibaba cobar www.github.com/alibaba/
    [Show full text]
  • Java Magazin 8.2007
    42846_ms_javaMa0707_weapons.indd1 1 Niederlande € 7,80 © 2007 Microsoft Corporation. Alle Rechte vorbehalten. 8.07 Deutschland € 6,50 Österreich € 7,50 Schweiz sFr 12,70 Ihr Potenzial. Unser Antrieb. VERSCHAFFEN SIE SICH DIE RICHTIGE WAFFE, BEVOR BEVOR WAFFE, RICHTIGE DIE SICH SIE VERSCHAFFEN OSGi – Die Zukunft Javas? Javas? Zukunft Die – OSGi SIE SICH DIESER WEBANWENDUNG STELLEN. WEBANWENDUNG DIESER SICH SIE Internet & Enterprise Technology www.javamagazin.de • SOA mit Open Source Source Open mit SOA Auf Testversionen & more • JAX-TV: Interview mit Dierk König • Ivy 1.4.1 CD • TeamCity 2.1 • Apache Forrest 0.8 • Groovy 1.0 • DbUnit 2.2 ➔ Lesen Sie im Heft ab Seite 67! • Alle Infos auf S. 3 JSF in großen Projekten Projekten großen in JSF • Reporting unternehmensweit unternehmensweit Reporting OSGi Die Zukunft Javas? ➔ Komponenten in Java, jetzt aber richtig! ➔ Mit Eclipse OSGi-Bundles entwerfen • JSR 275: Internationale wissenschaftliche Formate Formate wissenschaftliche Internationale 275: JSR SOA mit Open Source Was leisten die freien Tools? JSF im Härtetest Praxis in großen Projekten • ASP.NET AJAX Control Toolkits von Visual Studio von AJAX Toolkits Control ASP.NET Sie diese: Mit den standardkonformen Meistern gestalten. Webseiten interaktive beeindruckende, Herausforderung: Ihre Tools unter unter Tools und Tipps Mehr aufzunehmen. Browser jedem mit es bereit, Spring-Avalon-Migration Spring-Avalon-Migration Reporting unternehmensweit Herausforderungsmeister.de Ein Bericht sagt mehr als 1.000 Zeilen Zahlen & Fakten • Crossmedia mit XML mit Crossmedia JSR 275: Internationale wissenschaftliche Formate Spring-Framework ® Avalon-Spring-Migration – sind Sie 15.05.2007 15:44:46 Uhr ein Praxisbericht Crossmedia mit XML Apache Forrest bedient viele Formate 7 86 45 D Open Source SOA Realisierung einer serviceorientierten Architektur auf der Basis von Open Source SOA auf die leichte Art VON WOLFGANG PLEUS Derzeit positionieren sich die Großen der Branche als Anbieter von Plattformen für serviceorientierte Architek- turen (SOA).
    [Show full text]