DOCSLIB.ORG

Vaadin Programming Cookbook I

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Vaadin Programming Cookbook I Vaadin Programming Cookbook i Vaadin Programming Cookbook Vaadin Programming Cookbook ii Contents 1 Vaadin Architecture Tutorial 1 1.1 The tools.......................................................1 1.2 Introduction......................................................1 1.3 Prerequisites......................................................1 1.4 Set up the project...................................................2 1.5 The Architecture...................................................3 1.5.1 The layers...................................................3 1.5.1.1 Client Widgets...........................................4 1.5.1.2 Web Server Layer.........................................4 1.5.1.3 Persistence Layer.........................................4 1.5.2 Our project explained.............................................5 1.5.2.1 Persistence.............................................5 1.5.2.2 Web Server Layer.........................................5 1.5.2.3 Client Tier.............................................8 1.6 Complete Source Code................................................9 1.7 Running the example................................................. 11 1.8 Results......................................................... 11 1.9 Download the Source Code.............................................. 12 2 Vaadin Example Application 13 2.1 The tools....................................................... 13 2.2 Introduction...................................................... 13 2.3 Prerequisites...................................................... 13 2.4 Set up the project................................................... 14 2.5 Coding the example.................................................. 15 2.6 The complete source code.............................................. 21 2.7 Running the example................................................. 25 2.8 Results......................................................... 26 2.9 Download the Source Code.............................................. 26 Vaadin Programming Cookbook iii 3 Vaadin Best Practices 27 3.1 The tools....................................................... 27 3.2 Introduction...................................................... 27 3.3 Prerequisites...................................................... 27 3.4 Set up the project................................................... 27 3.5 The example...................................................... 29 3.5.1 Make a design................................................ 29 3.5.2 Annotations.................................................. 30 3.5.3 Navigator................................................... 30 3.5.3.1 Layout & content......................................... 30 3.5.3.2 Navigator views.......................................... 31 3.5.3.3 Menu listeners........................................... 31 3.5.3.4 Menu................................................ 31 3.5.3.5 Navigator initial page....................................... 32 3.5.3.6 Welcome page........................................... 32 3.5.4 Validate user input.............................................. 33 3.5.4.1 Input form............................................. 33 3.5.4.2 Name field validator........................................ 33 3.5.4.3 Surname field validator...................................... 33 3.5.4.4 Age field validator......................................... 34 3.5.4.5 Age field validator......................................... 34 3.5.4.6 Validation process......................................... 34 3.5.4.7 Clear fields............................................. 35 3.5.5 Use containers in fields............................................ 35 3.5.5.1 Property sets............................................ 36 3.5.5.2 Field groups............................................ 36 3.5.6 Separate the UI from the data........................................ 36 3.5.7 Deploy on https................................................ 38 3.6 The complete source code.............................................. 38 3.6.1 VaadinbestpracticesUI.java.......................................... 38 3.6.2 WelcomePage.java.............................................. 39 3.6.3 InputPage.java................................................ 40 3.6.4 DataPage.java................................................. 42 3.6.5 DataBean.java................................................ 43 3.7 Running the example................................................. 43 3.8 Results......................................................... 43 3.8.1 Welcome view................................................ 43 3.8.2 Input view.................................................. 44 3.8.3 Input view.................................................. 45 3.9 Download the Source Code.............................................. 46 Vaadin Programming Cookbook iv 4 Vaadin Visual Designer Example 47 4.1 The tools....................................................... 47 4.2 Introduction...................................................... 47 4.3 Prerequisites...................................................... 47 4.4 Set up the project................................................... 47 4.4.1 Get the Visual Designer........................................... 47 4.4.2 Create the project............................................... 49 4.5 Coding the example.................................................. 57 4.6 The complete source code.............................................. 61 4.7 Running the example................................................. 63 4.8 Results......................................................... 64 4.9 Download the Source Code.............................................. 64 5 Vaadin Data Binding Example 65 5.1 The tools....................................................... 65 5.2 Introduction...................................................... 65 5.3 Prerequisites...................................................... 65 5.4 Set up the project................................................... 65 5.5 Coding the example.................................................. 67 5.6 The complete source code.............................................. 72 5.7 Running the example................................................. 75 5.8 Results......................................................... 75 5.9 Download the Source Code.............................................. 77 6 Vaadin Rest Example 78 6.1 Introduction...................................................... 78 6.2 Prerequisites...................................................... 78 6.3 Set up the server project............................................... 78 6.3.1 Download Jersey............................................... 78 6.3.2 Create the server project........................................... 79 6.3.3 Copy Jersey Files............................................... 80 6.4 Coding the server................................................... 81 6.5 The server web.xml.................................................. 82 6.6 Create the client project................................................ 83 6.7 Coding the client project............................................... 84 6.7.1 Client Class to access the server....................................... 84 6.7.2 Vaadin UI................................................... 86 6.8 The complete source code.............................................. 87 6.8.1 The server source code............................................ 87 Vaadin Programming Cookbook v 6.8.2 The client Source Code............................................ 88 6.9 Running the example................................................. 91 6.10 Results......................................................... 92 6.10.1 Get the response............................................... 92 6.10.2 Get the plain text............................................... 93 6.10.3 Get the XML................................................. 94 6.10.4 Get the JSON................................................. 95 6.11 Download the Source Code.............................................. 95 7 Vaadin Container Example 96 7.1 The tools....................................................... 96 7.2 Introduction...................................................... 96 7.3 Prerequisites...................................................... 96 7.4 Set up the project................................................... 97 7.5 Coding the example.................................................. 98 7.5.1 MyBean BeanContainer........................................... 98 7.5.2 MySubBean BeanContainer......................................... 99 7.5.3 The UI.................................................... 100 7.5.3.1 Random name generator...................................... 100 7.5.3.2 The layout............................................. 101 7.5.3.3 First BeanContainer........................................ 101 7.5.3.4 Second BeanContainer...................................... 101 7.5.3.5 Employee Table.......................................... 101 7.5.3.6 Doe’s Table............................................ 102 7.5.3.7 Dynamic input........................................... 102 7.5.3.8 Click listener............................................ 102 7.5.3.9 Find Duplicates.......................................... 103 7.6 The complete source code.............................................. 103 7.7 Running the example................................................
Load more

Recommended publications
  • Modern Web Application Frameworks
    MASARYKOVA UNIVERZITA FAKULTA INFORMATIKY Û¡¢£¤¥¦§¨ª«¬­Æ°±²³´µ·¸¹º»¼½¾¿Ý Modern Web Application Frameworks MASTER’S THESIS Bc. Jan Pater Brno, autumn 2015 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or ex- cerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Bc. Jan Pater Advisor: doc. RNDr. Petr Sojka, Ph.D. i Abstract The aim of this paper was the analysis of major web application frameworks and the design and implementation of applications for website content ma- nagement of Laboratory of Multimedia Electronic Applications and Film festival organized by Faculty of Informatics. The paper introduces readers into web application development problematic and focuses on characte- ristics and specifics of ten selected modern web application frameworks, which were described and compared on the basis of relevant criteria. Practi- cal part of the paper includes the selection of a suitable framework for im- plementation of both applications and describes their design, development process and deployment within the laboratory. ii Keywords Web application, Framework, PHP,Java, Ruby, Python, Laravel, Nette, Phal- con, Rails, Padrino, Django, Flask, Grails, Vaadin, Play, LEMMA, Film fes- tival iii Acknowledgement I would like to show my gratitude to my supervisor doc. RNDr. Petr So- jka, Ph.D. for his advice and comments on this thesis as well as to RNDr. Lukáš Hejtmánek, Ph.D. for his assistance with application deployment and server setup. Many thanks also go to OndˇrejTom for his valuable help and advice during application development.
    [Show full text]
  • Alfresco ACSCE-5X Exam
    Alfresco ACSCE-5X Exam Volume: 60 Questions Question: 1 What is the class.org.alfresco.model.ContentModel used for? A. Transforming document content into a different format. B. Validating the content of the document follows a certain template. C. Referencing out of the box content model types in your code. D. Trigger automatic metadata extraction from the content. E. Moving content in the repository between folders. Answer: C Question: 2 When would you consider developing your custom server code in Java in place of JavaScript? (Choose three.) A. When a web script needs to be executed inside a transaction. B. When I need to execute part of my code as system user. C. When developing a custom scheduled process. D. When developing a content rule. E. When developing a behavior/policy. Answer: B,C,D Question: 3 Which file is required in order for an AMP file to be valid? A. module.properties B. service-context.xml Leading the way in IT testing and certification tools, www.examkiller.net Alfresco ACSCE-5X Exam C. file-mapping.properties D. web.xml Answer: A Question: 4 An Alfresco Webscript is called via a POST request to the URL /example/mycontent/item1, relative to the Alfresco Content Services REST API base URL. Based on RESTful principles and standards, what will be the result of this call? A. The existing resource ‘item1’ is updated. B. The existing resource ‘item1’ is updated. C. The content of the resource ‘item1’ is returned to the user. D. A new resource ‘item1’ is added. Answer: D Question: 5 How can we modify what data is shown in each row of the Alfresco Share document library, using the supported extension points? A.
    [Show full text]
  • IP Log for Eclipse.Platform Release 4.0, July 2010 Licenses
    IP Log for eclipse.platform Release 4.0, July 2010 Licenses • Eclipse Public License v1.0 Third-Party Code CQ Third-Party Code License Use ICU4J (core and extended ICU4J License (X License, 1065 function) and ICU4J MIT Style) Replacement plug-in Version: 3.6 ICU4J License (X License, 1116 ICU4J Version: 3.4.5.20061213 MIT Style) 1153 JSch 0.1.31 Version: 0.1.31 New BSD license Apache Lucene Version: 1.9.1 243 (Core+Contrib Analyzers Apache License, 2.0 Analysis Src) 257 APT Version: 1 New BSD license Mozilla Public License 1.1 (MPL), MIT Style with No 262 Cairo Version: 1.0.2 Endorsement Clause, Historical Permissive Notice & Disclaimer ICU4J License (X License, 280 ICU4J Version: 3.4 MIT Style) ICU4J License (X License, 281 ICU4J Version: 3.4.3 MIT Style) 293 jsch Version: 0.1.28 New BSD license 308 PNG unload Version: 1 MIT license 1232 Apache Ant Version: 1.7.0 Apache License, 2.0 ICU4J and ICU4J Replacement ICU4J License (X License, 1367 Version: 3.6.1 MIT Style) Olsen time zone data Version: 1368 Public Domain 2007e Work derived from IJG JPEG 1596 IJG License Version: Release 6b,337 unmodified 1826 JSch 0.1.35 New BSD license source & binary ICU4J and ICU4J replacement MIT License with "no unmodified 1919 Version: 3.8.1 edorsement" clause source & binary unmodified 2014 jsch Version: 0.1.37 New BSD license source & binary XHTML DTDs Version: unmodified 2044 W3C Document License Versions 1.0 and 1.1 (PB CQ331) source org.apache.ant Version: 1.6.5 2404 (ATO CQ1013) (using Orbit Apache License, 2.0 CQ2209) org.apache.lucene Version: 1.4.3 2405 (Core Source Only) (ATO Apache License, 2.0 CQ1014) (using Orbit CQ2210) Junit Version: 3.8.2 (ATO 2406 Common Public License 1.0 CQ299) (using Orbit CQ2206) Historical support for Java SSH modified 2410 Applet + Blowfish Version - v.
    [Show full text]
  • Cross-Domain Embedding for Vaadin Applications
    Cross-Domain Embedding for Vaadin Applications Janne Lautamäki and Tommi Mikkonen Department of Software Systems, Tampere University of Technology, Korkeakoulunkatu 1, FI-33720 Tampere, Finland {janne.lautamaki,tommi.mikkonen}@tut.fi Abstract. Although the design goals of the browser were originally not at running applications or at displaying a number of small widgets on a single web page, today many web pages considerably benefit from being able to host small embedded applications as components. While the web is full such applications, they cannot be easily reused because of the same origin policy restrictions that were introduced to protect web content from potentially malicious use. In this paper, we describe a generic design for cross domain embedding of web applications in a fashion that enables loading of applications from different domains as well as communication between the client and server. As the proof- of-concept implementation environment, we use web development framework Vaadin, a Google Web Toolkit based system that uses Java for application development. Keywords: Vaadin, JSONP, cross-domain applications. 1 Introduction Web applications – systems that resemble desktop applications in their behavior but are run inside the browser – are becoming increasingly common. The current trend is that web pages have dynamic components side by side with the traditional web content, such as static text and images. These dynamic components can be small widgets that for instance display current weather information or stock exchange data, or even full-fledged web applications that offer a service related to the theme of the web page where they are located [1]. Creating dynamic web pages is much more complex than building plain old web pages.
    [Show full text]
  • Technology MX4 Technology MX4, Based in Canada, Is a Company That Works in the Field of Optimization Technologies for Complex Problems
    Technology MX4 Technology MX4, based in Canada, is a company that works in the field of optimization technologies for complex problems. About MX4 Technology MX4 is specialized in the development of web applications for K12 schools, which also includes providing training and user support. ZK x MX4 ZK is used in our main product called Trapeze School for the automatic creation of school timetables. The SAAS application targets K12 schools and can handle multiple school configuration and constraints. This tool is offered in 2 languages (French and English) and is being used by more than 150 schools across Quebec. “Simplicity (AJAX) and rapid The team is composed of 5 engineers; 1 for the User interface using development.” ZK and the others are working on the backend micro-services and AI engine. We started the project in 2011 and we have an ongoing delivery process to offer new features every 6 months. We use the following technologies in the project: ZK, Hibernate, Tomcat, Rest, Kafka, ActiveMQ and PostgreSQL. Why ZK We evaluated developing our web application in JSP and we built a small, but complete application that includes our principal needs using 3 different frameworks: OpenXava, Vaadin and ZK. ZK was the easiest and fastest one. ZK was the easiest to use in the sense that it hides and handles the AJAX part, so you don’t have to worry about passing information between the server and the client. As a result it saves the developing ZK – THE SIMPLEST WAY TO MAKE WEB APPLICATIONS RICH 2 CASE STUDY time a lot so we decide to go with ZK.
    [Show full text]
  • Programming Technologies for the Development of Web-Based Platform for Digital Psychological Tools
    (IJACSA) International Journal of Advanced Computer Science and Applications, Vol. 9, No. 8, 2018 Programming Technologies for the Development of Web-Based Platform for Digital Psychological Tools Evgeny Nikulchev1, Dmitry Ilin2 Pavel Kolyasnikov3 Ilya Zakharov5, Sergey Malykh6 4 MIREA – Russian Technological Vladimir Belov Psychological Institute of Russian University & Russian Academy Russian Academy Science Academy of Education Science, Moscow, Russia Moscow, Russia Moscow, Russia Abstract—The choice of the tools and programming In addition, large accumulated data sets can become the technologies for information systems creation is relevant. For basis for machine learning mechanisms and other approaches every projected system, it is necessary to define a number of using artificial intelligence. Accumulation of data from criteria for development environment, used libraries and population studies into a single system can allow a technologies. The paper describes the choice of technological breakthrough in the development of systems for automated solutions using the example of the developed web-based platform intellectual analysis of behavior data. of the Russian Academy of Education. This platform is used to provide information support for the activities of psychologists in The issue of selecting methodological tools for online and their research (including population and longitudinal offline research includes several items. researches). There are following system features: large scale and significant amount of developing time that needs implementation First, any selection presupposes the existence of generally and ensuring the guaranteed computing reliability of a wide well-defined criteria, on the basis of which a decision can be range of digital tools used in psychological research; ensuring made to include or not to include techniques in the final functioning in different environments when conducting mass toolkit.
    [Show full text]
  • Vaadin Custom Training
    STORY AND PHILOSOPHY Software is eating the world and what most of us see of it is the user interface. The user interface has become the key component of how the users experience the business behind it. Competition is lost or won due to user experience. Simplicity is king and the users get frustrated by anything ugly, slow or not working on the device they happen to use at the time. We at Vaadin fight for simplicity and invite everyone to join this fight. Together we want to build a user interface that puts a smile on the user’s face. Vaadin is the technology that empowers developers to build the best web-apps for business purposes. Our priority over everything else is developer productivity because we believe that by simplifying the developer experience and saving the developer’s time, they are best able to focus on building great user interfaces. Our brand is what we want everyone to think about us. When everyone - both us and the people around us - have a consistent understanding of what Vaadin is and what we Custom Training stand for, it enables that image to spread and amplify. This book defines what we want that image to be. It defines what the Vaadin brand is. I hope that You are as excited and proud of living and breathing the Vaadin brand as PRESENTER I am. You are the one who is shaping what everyone thinks about Vaadin - using this brand as a tool and a guideline every day. Sami Kaksonen Let’s fight for simplicity for both the users and the developers! [email protected] Joonas Lehtinen Founder & CEO Vaadin INTRODUCTION 5 TABLE
    [Show full text]
  • Choosing the Right Front-End Framework
    Choosing the right front-end framework Janko Ulaga, Tomislav Naki ć-Alfirevi ć May 2013 Introduction - needed to upgrade our UI - choosing the right framework: a challenge! - currently around 30 Java frameworks - not a simple process, many different criteria to consider * certain frameworks suggest or encourage certain technologies...not so good, right? UI prototype description - monitor & control system - table showing real time device state changes - graph showing parameter updates - form to set device parameter values Criteria - technical vs. business - in-house knowledge is great, but... - analyze & consider everything: in-house procedures, development, HTML5, licensing, testing, integration... Criteria - JSF & Vaadin for Java - ExtJS & AngularJS for JavaScript Vaadin Java Server Angular JS ExtJS Faces Popularity(# of 246,000 1,220,000 110,000 1,000,000 Google searches/ month) Learning( # of ~20 ~220 ~50 ~40 books on Amazon) Requires No but some No No Yes development components do license Java Server Faces Basics - component-driven UI design model, XML templates - requests processed by the FacesServlet which does all the heavy lifting - convention over configuration - inversion of control *great for rapid development, but lacks “shiny” components Which JSF framework? - popularity, showcases, extensions... - we chose Primefaces Vaadin Basics - code in Java - uses GWT for web page rendering - extensible components set - server side application logic Implementation - Primefaces - environment setup - easy design: one view/action subset – one backing bean - great to use with Twitter Bootstrap - easy to combine JavaScript *push component cannot connect to remote URL - quick solution with PE Extensions - high network traffic Implementation - Vaadin - environment setup - two additional plugins, charts and push - nice API - works great on all browsers - no need for JavaScript *not so good performance-wise, bad choice for real- time apps.
    [Show full text]
  • Curriculum Vitae – Onno Scheffers
    Curriculum Vitae – Onno Scheffers Curriculum Vitae Onno Scheffers Title: B.Sc. Nationality: Dutch th Birthdate: November 20 1974 Gender: Male Drivers license: A & B Onno Scheffers is a software developer in heart and soul. He knew he wanted to program at an early age. After finishing Atheneum (pre-university secondary education) and applied computer science at Hogeschool Rotterdam & Omstreken, Onno further specialized himself and became a certified Java specialist (SCJP, SCWCD, OCA, OCP). With over 17 years of professional experience as a Java developer, Onno is always on the lookout for new technical challenges. He’s flexible and works well in teams. Onno also likes training and supporting other developers. Whether it’s mobile applications, desktop application or enterprise web applications, Onno has helped many clients finish their projects successfully. 1/10 Curriculum Vitae – Onno Scheffers Education & Certification October 2017 Machine Learning by Stanford University on Coursera Certified with a 96.5% grade. June 2016 Oracle Certified Professional, Java SE 7 Programmer Passed the OCP exam with a 81% score. November 2015 Xebia - Scala Training May 2015 Oracle Certified Associate, Java SE 7 Programmer Passed the OCA exam with a 96% score. April 2014 Vaadin 7 Certified Developer Attended the Vaadin Fundamentals training and the Vaadin Advanced training in April and took the Vaadin certification in July. May 2011 Hippo CMS 7 Developer Training Two day Hippo CMS training at Hippo HQ in Amsterdam. April 2010 Sun Certified Programmer for the Java Platform, Standard Edition 6 Passed the exam with a score of 95%. March 2005 Sun Certified Web Component Developer for the Java 2 Platform, Enterprise Edition 1.4 January 2004 JBoss Advanced Training Internal JBoss training by Finalist IT-Group, with focus on configuration.
    [Show full text]
  • Vaadin-Intro.Pdf
    Vaadin introduction7 Intro to Vaadin new Label(“Hello world”) What’s QA new Getting started User interface framework for rich web applications User Interface Components Developer Rich Productivity UX java html 12Key Ideas3 Rich Components1 User Interface Data Source Theme 1.6 Going mobile GWT is a versatile technology that allows developers to create application UI for desktop, tablet, and mobile consumption. As can be expected, over 98% of apps support desktop browsers, but we found it interesting that tablets had overtaken phones (at least when it came to support from GWT-based apps). In US, the number of apps supporting tablets was as high as 46%, while it was just 34% in Europe. Desktop browsers 1.6 Going mobile GWT is a versatile technology that allows developers to create application UI for 1.6 Going mobile desktop, tablet, and mobile consumption. As can be expected, over 98% of apps “Since gwt is used extensively support desktop browsers, but we found it interesting that tablets had overtaken GWT is a versatile technology that allows developers to create application UI for phones (at least when it came to support from GWT-based apps). In US, the number in the enterprise, this may of apps supporting tablets was as high as 46%, while it was just 34% in Europe. 98.1%desktop, tablet, and mobile consumption. As can be expected, over 98% of apps explain why tablets are more support desktop browsers, but we found it interesting that tabletsTablets had overtaken Tablets phones (at least when it came to support from GWT-based apps).
    [Show full text]
  • Rich Web Applications in Server-Side Java Without Plug-Ins Or Javascript
    Rich Web Applications in Server-side Java without Plug-ins or JavaScript Joonas Lehtinen, PhD Vaadin Ltd - CEO vaadin.com/vaadin @joonaslehtinen Rich Web Applications in Server-side Java without Plug-ins or JavaScript Joonas Lehtinen, PhD Vaadin Ltd - CEO vaadin.com/vaadin @joonaslehtinen ? Vaadin is a UI framework for rich web applications java html History behind Vaadin healthcare portal, >100 kloc of perl, .. web 1.0, netscape, ie5, ie6, ... 1998 healthcare portal, 100 kloc of perl, .. web 1.0, netscape, ie5, ie6, ... thinking of object oriented design, desktop, Java, U and I ... desktop programming paradigm for web! found desktop programming paradigm for web! found 2000 millstone ajax google web toolkit re-released as 2002 2005 2008 millstone ajax goolge web toolkit re-released as 2009 Used by >50.000 developers in >150 countries Building apps for fortune 500, startups, governments, ... across all industries Collaborating by conributing > 200 plug-ins and helping plug-ins, mainstream each other on a forum with >1500 posts / m 2010 2011 Backed by 50+ person full-time team see our transparent vaadin.com/roadmap 2012 Apache License Contents Server-side Discussion RIA What is it? Pros & cons? Vaadin Technology, Features, Getting started In practice Coding a Vaadin application step-by-step Server-side RIA “Web 1.0” Client Server 5 HTML Page DOM over HttpResponse View 4 Model 3 Parameters over HttpRequest Controller 2 DB 1 client-side ria fat client Client-side RIA Client 4 Server Requested data View to view as XML / JSON 5 DOM Model 3 1
    [Show full text]
  • Declarative Ajax Web Applications Through SQL++ on a Unified
    Declarative Ajax Web Applications through SQL++ on a Unified Application State Yupeng Fu Kian Win Ong Yannis Papakonstantinou UCSD UCSD UCSD [email protected] [email protected] [email protected] Abstract (c) the data tier in the database. Multiple mundane low-level tasks Implementing even a conceptually simple web application requires need to be performed in a coordinated fashion across all three tiers. an inordinate amount of time. FORWARD addresses three prob- The resulting problems (as follows) reduce developer productivity: Impedance mismatch lems that reduce developer productivity: (a) 1. Impedance mismatch arises because each tier uses different lan- across the multiple languages used at different tiers of the appli- guages (and data models) [5, 21]. The visual tier uses DOM Distributed data access cation architecture. (b) across the multi- (XHTML) / JavaScript (JSON); the application logic tier uses ple data sources of the application (user input of the browser page, an application programming language, such as Java, Python or Asyn- session data in the application server, SQL database etc). (c) PHP (objects); the data tier uses SQL (tables). To display a page, chronous, incremental modification of the pages , as performed by mundane and error-prone code is needed to translate SQL tables Ajax actions. into Java objects, and then into HTML / JavaScript objects. To FORWARD belongs to a novel family of web application frame- implement an action invocation, more code is needed to translate works that attack impedance mismatch by offering a single uni- in the opposite direction. fying language. FORWARD’s language is SQL++, which is SQL with necessary extensions for semi-structured data.
    [Show full text]