DOCSLIB.ORG

Specification of Manifest AUTOSAR AP Release 18-03

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Specification of Manifest AUTOSAR AP Release 18-03 Specification of Manifest AUTOSAR AP Release 18-03 Document Title Specification of Manifest Document Owner AUTOSAR Document Responsibility AUTOSAR Document Identification No 713 Document Status Final Part of AUTOSAR Standard Adaptive Platform Part of Standard Release 18-03 Document Change History Date Release Changed by Description AUTOSAR 2018-03-29 18-03 Release • Time Synchronization Management • DDS Deployment • Optional elements in Service Interfaces • Interaction with web services AUTOSAR • Secure Communication 2017-10-27 17-10 Release • Support for interaction with crypto Management and persistency • Signal-to-Service translation • Support for E2E communication • Platform Health Management • Uploadable Software Package AUTOSAR 2017-03-31 17-03 Release • Initial release Management 1 of 602 Document ID 713: AUTOSAR_TPS_ManifestSpecification — AUTOSAR CONFIDENTIAL — Specification of Manifest AUTOSAR AP Release 18-03 2 of 602 Document ID 713: AUTOSAR_TPS_ManifestSpecification — AUTOSAR CONFIDENTIAL — Specification of Manifest AUTOSAR AP Release 18-03 Disclaimer This work (specification and/or software implementation) and the material contained in it, as released by AUTOSAR, is for the purpose of information only. AUTOSAR and the companies that have contributed to it shall not be liable for any use of the work. The material contained in this work is protected by copyright and other types of intel- lectual property rights. The commercial exploitation of the material contained in this work requires a license to such intellectual property rights. This work may be utilized or reproduced without any modification, in any form or by any means, for informational purposes only. For any other purpose, no part of the work may be utilized or reproduced, in any form or by any means, without permission in writing from the publisher. The work has been developed for automotive applications only. It has neither been developed, nor tested for non-automotive applications. The word AUTOSAR and the AUTOSAR logo are registered trademarks. 3 of 602 Document ID 713: AUTOSAR_TPS_ManifestSpecification — AUTOSAR CONFIDENTIAL — Specification of Manifest AUTOSAR AP Release 18-03 Table of Contents 1 Introduction 12 1.1 Modeling Approach............................. 13 1.2 The Term Service.............................. 14 1.3 Abbreviations................................ 15 1.4 Document Conventions........................... 17 1.5 Requirements Tracing........................... 19 1.6 Known Limitations............................. 24 2 Big Picture of Manifest Definition 25 2.1 Design vs. Deployment........................... 25 2.2 About Manifest............................... 25 2.3 Serialization Format............................ 25 2.4 Scope.................................... 26 2.5 Manifests described in this Document.................. 27 3 Application Design 29 3.1 Overview................................... 29 3.2 Software Component............................ 29 3.3 Data Type.................................. 31 3.3.1 Overview............................. 31 3.3.2 ApplicationDataType....................... 31 3.3.2.1 String Data Type.................... 32 3.3.2.2 Associative Map Data Type.............. 35 3.3.2.3 Attributes of SwDataDefProps............. 40 3.3.3 ImplementationDataType.................... 42 3.3.3.1 String Data Type.................... 44 3.3.3.2 Vector Data Type.................... 47 3.3.3.3 Associative Map Data Type.............. 56 3.3.3.4 Attributes of SwDataDefProps............. 60 3.3.4 CppImplementationDataType.................. 62 3.3.4.1 Disclaimer........................ 62 3.3.4.2 Overview........................ 62 3.3.4.3 Attributes of SwDataDefProps............. 72 3.3.4.4 Fundamental Data Types............... 74 3.3.4.5 String Data Type.................... 74 3.3.4.6 Array Data Type..................... 76 3.3.4.7 Vector Data Type.................... 79 3.3.4.8 Struct Data Type.................... 82 3.3.4.9 Enumeration Data Type................ 83 3.3.4.10 Map Data Type..................... 84 3.3.4.11 Variant Data Type.................... 86 3.3.5 BaseType............................. 86 3.3.5.1 Bitfield.......................... 88 3.3.5.2 Enumeration...................... 89 4 of 602 Document ID 713: AUTOSAR_TPS_ManifestSpecification — AUTOSAR CONFIDENTIAL — Specification of Manifest AUTOSAR AP Release 18-03 3.4 Service Interface.............................. 90 3.4.1 Overview............................. 90 3.4.2 Event............................... 93 3.4.3 Field................................ 94 3.4.4 Method.............................. 94 3.4.4.1 Fire and Forget Method................ 95 3.4.5 Compatibility of Service Interfaces............... 96 3.4.6 Namespace........................... 98 3.4.7 Error Handling.......................... 101 3.4.8 Service Interface Data Type Mapping............. 103 3.5 Service Interface Mapping......................... 106 3.6 Service Interface Element Mapping.................... 111 3.6.1 Overview............................. 111 3.6.2 Service Interface Event Mapping................ 114 3.6.3 Service Interface Field Mapping................ 116 3.6.4 Service Interface Method Mapping............... 118 3.6.5 Service Interface Application Error Mapping......... 120 3.7 Persistency Interface............................ 122 3.7.1 Overview............................. 122 3.7.2 Persistency Key Value Database Interface.......... 124 3.7.3 Persistency File Proxy Interface................ 127 3.8 Time Synchronization Interface...................... 129 3.9 Platform Health Management Interface.................. 133 3.9.1 Overview............................. 133 3.9.2 Supervised Entities and Checkpoints............. 134 3.9.3 Health Channels......................... 136 3.10 Interaction Endpoint for Application.................... 138 3.10.1 Service-oriented Communication................ 138 3.10.2 Interaction with Crypto Software................ 139 3.10.3 Interaction with Persistent Key-Value Storage......... 141 3.10.4 Interaction with Persistent File-Based Storage........ 142 3.10.5 Port Prototype Props...................... 142 3.10.6 Port Prototype ComSpec.................... 145 3.10.6.1 Port Prototypes typed by Service Interfaces..... 145 3.10.6.2 Port Prototypes typed by Persistency Data Interfaces 153 3.11 Executable Group.............................. 157 3.12 Optional Members in complex Data Structures.............. 165 3.12.1 Background........................... 165 3.12.2 Definition of Optionality..................... 166 3.13 Serialization Properties........................... 173 3.13.1 Default Values for Serialization Properties........... 174 3.13.2 Individual Definition of Serialization Properties........ 179 3.13.3 Assignment of TLV Data IDs for Data Structures with optional Members............................. 186 4 Diagnostic Mapping 190 5 of 602 Document ID 713: AUTOSAR_TPS_ManifestSpecification — AUTOSAR CONFIDENTIAL — Specification of Manifest AUTOSAR AP Release 18-03 4.1 Overview................................... 190 4.2 Diagnostic Data Mapping......................... 194 4.3 Diagnostic Software Mapping....................... 197 4.4 Diagnostic Event to Port Mapping..................... 202 4.5 Diagnostic Operation Cycle to Port Mapping............... 204 4.6 Diagnostic Enable Condition to Port Mapping.............. 207 4.7 Diagnostic Storage Condition to Port Mapping.............. 210 5 REST Design 212 5.1 Overview................................... 212 5.2 REST Service Interface.......................... 215 5.3 REST Resource............................... 215 5.4 REST Element............................... 220 6 Application Manifest 229 6.1 Overview................................... 229 6.2 Startup Configuration............................ 231 6.2.1 Mode-dependent Startup Configuration............ 232 6.2.2 Scheduling............................ 235 6.2.3 Startup Options......................... 236 6.2.4 Resources............................ 239 6.2.5 Execution Dependency..................... 240 6.2.6 Assignment of Processes to Function Group states..... 241 7 Service Instance Manifest 242 7.1 Service Interface Deployment....................... 242 7.1.1 SOME/IP Service Interface Deployment............ 245 7.1.2 DDS Service Interface Deployment.............. 255 7.1.3 User Defined Service Interface................. 257 7.2 Service Instance Deployment....................... 261 7.2.1 SOME/IP Service Instance Deployment............ 267 7.2.1.1 Provided Service Instance............... 268 7.2.1.2 Required Service Instance............... 287 7.2.2 DDS Service Instance Deployment............... 297 7.2.2.1 Provided DDS Service Instance............ 298 7.2.2.2 Required DDS Service Instance............ 300 7.2.2.3 DDS Service Instance to Machine mapping..... 301 7.2.3 User Defined Service Instance Deployment.......... 302 7.3 EndToEndProtection............................ 304 7.4 Secure Communication.......................... 309 7.4.1 Secure Communication over TLS............... 312 7.4.2 Secure Communication over SecOC.............. 316 7.5 Log and Trace................................ 318 8 Machine Manifest 322 8.1 Hardware Resources............................ 325 8.2 Machine States............................... 329 6 of 602 Document ID 713: AUTOSAR_TPS_ManifestSpecification — AUTOSAR CONFIDENTIAL — Specification of Manifest AUTOSAR AP Release 18-03 8.3 Function Groups.............................. 331 8.4 State Timeouts..............................
Load more

Recommended publications
  • 4 Hash Tables and Associative Arrays
    4 FREE Hash Tables and Associative Arrays If you want to get a book from the central library of the University of Karlsruhe, you have to order the book in advance. The library personnel fetch the book from the stacks and deliver it to a room with 100 shelves. You find your book on a shelf numbered with the last two digits of your library card. Why the last digits and not the leading digits? Probably because this distributes the books more evenly among the shelves. The library cards are numbered consecutively as students sign up, and the University of Karlsruhe was founded in 1825. Therefore, the students enrolled at the same time are likely to have the same leading digits in their card number, and only a few shelves would be in use if the leadingCOPY digits were used. The subject of this chapter is the robust and efficient implementation of the above “delivery shelf data structure”. In computer science, this data structure is known as a hash1 table. Hash tables are one implementation of associative arrays, or dictio- naries. The other implementation is the tree data structures which we shall study in Chap. 7. An associative array is an array with a potentially infinite or at least very large index set, out of which only a small number of indices are actually in use. For example, the potential indices may be all strings, and the indices in use may be all identifiers used in a particular C++ program.Or the potential indices may be all ways of placing chess pieces on a chess board, and the indices in use may be the place- ments required in the analysis of a particular game.
    [Show full text]
  • JS and the DOM
    Back to the client side: JS and the DOM 1 Introduzione alla programmazione web – Marco Ronchetti 2020 – Università di Trento Q What are the DOM and the BOM? 2 Introduzione alla programmazione web – Marco Ronchetti 2020 – Università di Trento JS and the DOM When a web page is loaded, the browser creates a Document Object Model of the page, which is as a tree of Objects. Every element in a document—the document as a whole, the head, tables within the document, table headers, text within the table cells—is part of its DOM, so they can all be accessed and manipulated using the DOM and a scripting language like JavaScript. § With the object model, JavaScript can: § change all the HTML [elements, attributes, styles] in the page § add or remove existing HTML elements and attributes § react to HTML events in the page § create new HTML events in the page 3 Introduzione alla programmazione web – Marco Ronchetti 2020 – Università di Trento Using languages implementations of the DOM can be built for any language: e.g. Javascript Java Python … But Javascript is the only one that can work client-side. 4 Introduzione alla programmazione web – Marco Ronchetti 2020 – Università di Trento Q What are the fundamental objects in DOM/BOM? 5 Introduzione alla programmazione web – Marco Ronchetti 2020 – Università di Trento Fundamental datatypes - 1 § Node Every object located within a document is a node. In an HTML document, an object can be an element node but also a text node or attribute node. § Document (is-a Node) § the root document object itself.
    [Show full text]
  • Project 0: Implementing a Hash Table
    CS165: DATA SYSTEMS Project 0: Implementing a Hash Table CS 165, Data Systems, Fall 2019 Goal and Motivation. The goal of Project 0 is to help you develop (or refresh) basic skills at designing and implementing data structures and algorithms. These skills will be essential for following the class. Project 0 is meant to be done prior to the semester or during the early weeks. If you are doing it before the semester feel free to contact the staff for any help or questions by coming to the office hours or posting in Piazza. We expect that for most students Project 0 will take anything between a few days to a couple of weeks, depending in the student’s background on the above areas. If you are having serious trouble navigating Project 0 then you should reconsider the decision to take CS165. You can expect the semester project to be multiple orders of magnitude more work and more complex. How much extra work is this? Project 0 is actually designed as a part of the fourth milestone of the semester project. So after finishing Project 0 you will have refreshed some basic skills and you will have a part of your project as well. Basic Project Description. In many computer applications, it is often necessary to store a collection of key-value pairs. For example, consider a digital movie catalog. In this case, keys are movie names and values are their corresponding movie descriptions. Users of the application look up movie names and expect the program to fetch their corresponding descriptions quickly.
    [Show full text]
  • PAM: Parallel Augmented Maps
    PAM: Parallel Augmented Maps Yihan Sun Daniel Ferizovic Guy E. Belloch Carnegie Mellon University Karlsruhe Institute of Technology Carnegie Mellon University [email protected] [email protected] [email protected] Abstract 1 Introduction Ordered (key-value) maps are an important and widely-used The map data type (also called key-value store, dictionary, data type for large-scale data processing frameworks. Beyond table, or associative array) is one of the most important da- simple search, insertion and deletion, more advanced oper- ta types in modern large-scale data analysis, as is indicated ations such as range extraction, filtering, and bulk updates by systems such as F1 [60], Flurry [5], RocksDB [57], Or- form a critical part of these frameworks. acle NoSQL [50], LevelDB [41]. As such, there has been We describe an interface for ordered maps that is augment- significant interest in developing high-performance paral- ed to support fast range queries and sums, and introduce a lel and concurrent algorithms and implementations of maps parallel and concurrent library called PAM (Parallel Augment- (e.g., see Section 2). Beyond simple insertion, deletion, and ed Maps) that implements the interface. The interface includes search, this work has considered “bulk” functions over or- a wide variety of functions on augmented maps ranging from dered maps, such as unions [11, 20, 33], bulk-insertion and basic insertion and deletion to more interesting functions such bulk-deletion [6, 24, 26], and range extraction [7, 14, 55]. as union, intersection, filtering, extracting ranges, splitting, One particularly useful function is to take a “sum” over a and range-sums.
    [Show full text]
  • Chapter 6 : DATA TYPES
    Chapter 6 : DATA TYPES •Introduction • Primitive Data Types • Character String Types • User-Defined Ordinal Types • Array Types • Associative Arrays • Record Types • Union Types • Pointer Types Copyright © 2006 Pearson Addison-Wesley. All rights reserved. 6-1 Introduction •A data type defines a collection of data objects and a set of predefined operations on those objects • Evolution of data types: – FORTRAN I (1957) - INTEGER, REAL, arrays – Ada (1983) - User can create a unique type for every category of variables in the problem space and have the system enforce the types Copyright © 2006 Pearson Addison-Wesley. All rights reserved. 6-2 Introduction • Design issues for all data types: 1. What is the syntax of references to variables? 2. What operations are defined and how are they specified? Copyright © 2006 Pearson Addison-Wesley. All rights reserved. 6-3 1 Primitive Data Types • Those not defined in terms of other data types 1. Integer – Almost always an exact reflection of the hardware, so the mapping is trivial – There may be as many as eight different integer types in a language Copyright © 2006 Pearson Addison-Wesley. All rights reserved. 6-4 Primitive Data Types 2. Floating Point – Model real numbers, but only as approximations – Languages for scientific use support at least two floating-point types; sometimes more – Usually exactly like the hardware, but not always Copyright © 2006 Pearson Addison-Wesley. All rights reserved. 6-5 IEEE Floating Point Formats Copyright © 2006 Pearson Addison-Wesley. All rights reserved. 6-6 2 Primitive Data Types 3. Decimal – For business applications (money) – Store a fixed number of decimal digits (coded) – Advantage: accuracy – Disadvantages: limited range, wastes memory Copyright © 2006 Pearson Addison-Wesley.
    [Show full text]
  • A Short Course On
    Pointers Standard Libraries Classes ASHORT COURSE ON C++ Dr. Johnson School of Mathematics Semester 1 2008 university-logo Dr. Johnson C++ Pointers Standard Libraries Classes OUTLINE 1 POINTERS Why Pointers An Array is just a Pointer Pointers and Functions 2 STANDARD LIBRARIES Standard Containers 3 CLASSES Constructing a Class Using Classes Inheritance university-logo Dr. Johnson C++ Pointers Standard Libraries Classes OUTLINE 1 POINTERS Why Pointers An Array is just a Pointer Pointers and Functions 2 STANDARD LIBRARIES Standard Containers 3 CLASSES Constructing a Class Using Classes Inheritance university-logo Dr. Johnson C++ Pointers Standard Libraries Classes OUTLINE 1 POINTERS Why Pointers An Array is just a Pointer Pointers and Functions 2 STANDARD LIBRARIES Standard Containers 3 CLASSES Constructing a Class Using Classes Inheritance university-logo Dr. Johnson C++ Pointers Why Pointers Standard Libraries An Array is just a Pointer Classes Pointers and Functions OUTLINE 1 POINTERS Why Pointers An Array is just a Pointer Pointers and Functions 2 STANDARD LIBRARIES Standard Containers 3 CLASSES Constructing a Class Using Classes Inheritance university-logo Dr. Johnson C++ Pointers Why Pointers Standard Libraries An Array is just a Pointer Classes Pointers and Functions WHY DO WE NEED POINTERS? Pointers are an important mechanism in any computer program. Fortran pointers are hidden from the user. Pointers store the location of a value, rather than the value. 0xfff8 0xfff4 6 0xfff8 Memory a ptr_a Compiler 0xfff8 0xfff4 university-logo Dr. Johnson C++ Pointers Why Pointers Standard Libraries An Array is just a Pointer Classes Pointers and Functions USING POINTERS Declare pointers by putting * in front of the variable name.
    [Show full text]
  • Associative Arrays in C+ + Andrew Koenig AT&T Bell Laboratories 184 Liberty Corner Road; Warren NJ 07060; [email protected]
    Associative arrays in C+ + Andrew Koenig AT&T Bell Laboratories 184 Liberty Corner Road; Warren NJ 07060; [email protected] ABSTRACT An associative array is a one-dimensional array of unbounded size whose subscripts can be non-integral types such as character strings. Traditionally associated with dynamically typed languages such as AWK and SNOBOL4, associative arrays have applications ranging from compiler symbol tables to databases and commercial data processing. This paper describes a family of C+ + class definitions for associative arrays, including programming examples, application suggestions, and notes on performance. It concludes with a complete programming example which serves the same purpose as a well-known system command but is much smaller and simpler. 1. Introduction An associative array is a data structure that acts like a one-dimensional array of unbounded size whose subscripts are not restricted to integral types: it associates values of one type with values of another type (the two types may be the same). Such data structures are common in AWK[1] and SNOBOL4[2], but unusual in languages such as C[3], which have traditionally concentrated on lower-level data structures. Suppose that m is an associative array, or map, whose subscripts, or keys, are of type String and whose elements, or values, are integers. Suppose further that s and t are String variables. Then m[s] is an int called the value associated with s. In this example m[s] is an lvalue: it may be used on either side of an assignment. If s and t are equal, m[s] and m[t] are the same int object.
    [Show full text]
  • A Lightweight, Composable Metamodelling Language for Specification and Validation of Internal Domain Specific Languages
    A Lightweight, Composable Metamodelling Language for Specification and Validation of Internal Domain Specific Languages Markus Klotzb¨ucher and Herman Bruyninckx Department of Mechanical Engineering Katholieke Universiteit Leuven, Belgium [email protected] [email protected] Abstract. This work describes a declarative and lightweight metamod- elling framework called uMF for modelling and validating structural con- straints on programming language data-structures. By depending solely on the Lua language, uMF is embeddable even in very constrained em- bedded systems. That way, models can be instantiated and checked close to or even within the final run-time environment, thus permitting vali- dation to take the current state of the system into account. In contrast to classical metamodelling languages such as ECore, uMF supports open world models that are only partially constrained. We illustrate the use of uMF with a real-world example of a robot control formalism and compare it with a previously hand-written implementation. The results indicate that strict formalization was facilitated while flexibility and readability of the constraints were improved. 1 Introduction A domain specific language (DSL) is built specifically to express the concepts of a particular domain. Generally, two types of DSL can be distinguished accord- ing to the underlying implementation strategy. An external DSL is constructed from scratch, starting from definition of the desired syntax to implementation of the associated parser for reading it. In contrast, internal or embedded DSL are constructed on top of an existing host language [5] [16]. While this technique has been used for decades, in particular by the Lisp and Scheme communities, it has recently gained popularity through dynamic languages such as Ruby.
    [Show full text]
  • Pl Sql Array of Records Example
    Pl Sql Array Of Records Example Which Renard disrespect so indistinctively that Fredrick defends her kyle? Garth remains cold-blooded: she understock her brassiere subintroduced too digestedly? Suicidal and unsystematised Thornton airlifts her intensions wouldst playfully or indent gallingly, is Walsh cytogenetic? Avoid using this technology, and subsequently casted into the array of pl sql records example shows you still the rows from key can able to Process contents of collection here. You use the new type name in the declaration, the same as with predefined types such as NUMBER. REPLACE PACKAGE BODY SCOTT. Add your thoughts here. SQL implementation, as follows. When defining a VARRAY type, you must specify its maximum size with a positive integer. SQL record support are coming in the next major release. IS BEGIN IF truth IS NOT NULL THEN DBMS_OUTPUT. Nested table is a collection in which the size of the array is not fixed. Yes, I want to use it in loops. Holds set of partial rows from EMPLOYEES table. Having duplicate values in the subset results in false, if those duplicates are not present in the main set. FORALL supports the RETURNING bulk bind syntax. The systems requirements links off this site are no longer active on IBM. SQL programming language, namely PLPGSQL. If you find an error or have a suggestion for improving our content, we would appreciate your feedback. In the third case, the subscript is outside the legal range. You can make them persistent for the life of a database session by declaring the type in a package and assigning the values in a package body.
    [Show full text]
  • Chapter 6 Part 1
    Chapter 6 part 1 Data Types (updated based on 11th edition) ISBN 0-321—49362-1 Chapter 6 Topics • Introduction • Primitive Data Types • Character String Types • User-Defined Ordinal Types • Array Types • Associative Arrays • Record Types • Union Types • Pointer and Reference Types 2 Primitive Data Types • Almost all programming languages provide a set of primitive data types • Primitive data types: Those not defined in terms of other data types • Some primitive data types are merely reflections of the hardware • Others require only a little non-hardware support for their implementation 3 Primitive Data Types: Integer • Almost always an exact reflection of the hardware so the mapping is trivial • There may be as many as eight different integer types in a language • Java’s signed integer sizes: byte, short, int, long • Example integer type of unlimited length not supported by hardware? 4 Primitive Data Types: Floating Point • Model real numbers, but only as approximations • Languages for scientific use support at least two floating-point types (e.g., float and double; sometimes more • Usually exactly like the hardware, but not always • IEEE Floating-Point • Standard 754 5 Primitive Data Types: Complex • Some languages support a complex type, e.g., Fortran and Python • Each value consists of two floats, the real part and the imaginary part • Literal form (in Python): • (7 + 3j), where 7 is the real part and 3 is the imaginary part 6 Primitive Data Types: Decimal • For business applications (money) – Essential to COBOL – C# offers a decimal
    [Show full text]
  • Cmps401classnoteschap06.Pdf
    Chapter 6 Data Types 6.1 Introduction 236 6.2 Primitive Data Types 238 6.3 Character String Types 242 6.4 Enumeration Types 247 6.5 Array Types 250 6.6 Associative Arrays 261 6.7 Record Types 263 6.8 Tuple Types 266 6.9 List Types 268 6.10 Union Types 270 6.11 Pointer and Reference Types 273 6.12 Optional Types 285 6.13 Type Checking 286 6.14 Strong Typing 287 6.15 Type Equivalence 288 6.16 Theory and Data Types 292 Summary • Bibliographic Notes • Review Questions • Problem Set • Programming Exercises 294 CMPS401 Class Notes (Chap06) Page 1 / 36 Dr. Kuo-pao Yang Chapter 6 Data Types 6.1 Introduction 236 • A data type defines a collection of data values and a set of predefined operations on those values. • Computer programs produce results by manipulating data. • ALGOL 68 provided a few basic types and a few flexible structure-defining operators that allow a programmer to design a data structure for each need. • A descriptor is the collection of the attributes of a variable. • In an implementation a descriptor is a collection of memory cells that store variable attributes. • If the attributes are static, descriptor are required only at compile time. • These descriptors are built by the compiler, usually as a part of the symbol table, and are used during compilation. • For dynamic attributes, part or all of the descriptor must be maintained during execution. • Descriptors are used for type checking and by allocation and deallocation operations. 6.2 Primitive Data Types 238 • Those not defined in terms of other data types are called primitive data types.
    [Show full text]
  • Metamodelling and Metaprogramming
    Component-Based Software Engineering Exercise Sheet No. 1 Dipl.-Inf. Florian Heidenreich Software Technology Group Office Hours: Tuesdays, 1330–1430 hours Institute for Software and Multimedia Tech- INF 2080 nology http://st.inf.tu-dresden.de/teaching/cbse Department of Computer Science Technische Universit¨at Dresden 01062 Dresden Metamodelling and Metaprogramming Task 1: Reflection in Java (9 Points) 1a) Write a program that reads the name of a class from the command line and emits the interface of the class in Java syntax (interface or class, modifiers, constructors, methods, fields, no method bodies). Apply the program to a set of classes and interfaces as test input. Also use the program on itself. Hints: You can load a class whose name you know with java.lang.Class.forName(). java.- lang.Class offers a rich interface to allow you to inspect the interface of any class. 1b) Now write a program that reads a class name and a list of arguments from the command line, and creates an object of that class with the read arguments. Hints: Treat arguments as strings. A java.lang.Class can enumerate its constructors. Choose a constructor with the appropriate parameter count. Then, find the parameter types. To create typed argument objects, call the appropriate constructors that take a string as their only argument. Call dynamic constructors using java.lang.reflect.Constructor.newInstance(). 1c) Extend the solution of the previous task by reading a method name and a list of method arguments. Dynamically call the method on a newly created object. Use your program to invoke your solution from subtask (a) to print the interface of your solution of this subtask.
    [Show full text]