SlideShare a Scribd company logo

Dsl for-soa-artefacts

Guido Schmutz, profile picture
Guido Schmutz

The document discusses the use of domain-specific languages (DSLs) to simplify the creation of Service-Oriented Architecture (SOA) artifacts, highlighting their advantages over existing approaches like WSDL and XSD. It outlines the challenges faced in traditional service design, such as complexity and lack of standardization, and presents DSLs as a flexible solution that allows for more efficient modeling and automation. Additionally, it introduces the CBID-SAE meta model for SOA and mentions SOAML as a standard for modeling service-oriented architectures.

Technology
1 of 38
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
Using Domain Specific Language(s) to Simplify Creating SOA Artifacts SOA Symposium 2010 Guido Schmutz, Technology Manager / Partner Trivadis AG 5.10.2010, Berlin
Introduction Guido Schmutz Working for Trivadis for more than 13 years leading and independent IT service company operating in Germany, Austria and Switzerland Oracle ACE Director for Fusion Middleware and SOA Co-Author of different books Consultant, Trainer Software Architect for Java, Oracle, SOA and EDA More than 20 years of software development experience Contact: [email_address] Blog: http://guidoschmutz.wordpress.com/ Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
About Trivadis Swiss IT consulting company 13 locations in Switzerland, Germany and Austria ~ 540 employees Key figures 2009 Services for more than 650 clients in over 1'600 projects Over 150 service level agreements More than 5'000 training participants Research and development budget: CHF 6.0 Mio. / EUR 3.6 Mio.
Agenda Introduction Alternative ways to design service contract Domain Specific Languages (DSL) Eclipse Xtext Prototype Implementations Summary Using Domain Specific Language (s) to Simplify Creating SOA Artifacts Data are always part of the game.
„ Problem“ Most SOA platforms do not make a contract-first service design easy Creation of WSDL and XSD is too much effort There is build-in support in the IDE to graphically implement WSDL and XSD Platform specific, no standard for look-and-feel Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
„ Problem“ Lot of repetition Very talkative More options than (often) necessary => RPC/literal How to ensure Design guidelines WS-I compliance Asynchronous Interface Service versioning Ensure naming conventions Name of messages Name of port types Name of bindings So what are the other options? Using Domain Specific Language (s) to Simplify Creating SOA Artifacts <wsdl:definitions xmlns:tns=&quot;http://trivadis.com/service/credit-card/v1&quot; ... name=&quot;CreditCardValidation-v1&quot;> <wsdl:types> <xsd:schema ...> </wsdl:types> <wsdl:message name=&quot;validateCardRequest&quot;> <wsdl:part name=&quot;request&quot; element=&quot;tns:validateCreditCardPaymentRequest&quot;/> </wsdl:message> <wsdl:message name=&quot;validateCardResponse&quot;> <wsdl:part name=&quot;reply&quot; element=&quot;tns:validateCreditCardPaymentResponse&quot;/> </wsdl:message> <wsdl:message name=&quot;invalidCreditCardNumberFault&quot;> <wsdl:part name=&quot;error„ element=&quot;tns:invalidCreditCardNumberFault&quot;/> </wsdl:message> <wsdl:portType name=&quot;CreditCardValidationPT&quot;> <wsdl:operation name=&quot;validateCard&quot;> <wsdl:input message=&quot;tns:validateCardRequest&quot;/> <wsdl:output message=&quot;tns:validateCardResponse&quot;/> <wsdl:fault name=&quot;InvalidCreditCardNumberFault&quot; message=&quot;tns:invalidCreditCardNumberFault&quot;/> </wsdl:operation> </wsdl:portType> <wsdl:binding ...> <wsdl:service ...> </wsdl:definitions> <xs:schema xmlns:xs=„...&quot; xmlns:tns=&quot;http://www.trivadis.com/cdm/credit-card/v1&quot; targetNamespace= „http://www.trivadis.com/cdm/credit-card/v1 “ elementFormDefault=&quot;qualified&quot; attributeFormDefault=&quot;unqualified&quot; version=&quot;1.0&quot;> <xs:element name=&quot;creditCard&quot; type=&quot;tns:CreditCardT&quot;/> <xs:complexType name=&quot;CreditCardT&quot;> <xs:sequence> <xs:element name=&quot;creditCardKind&quot; type=&quot;tns:CreditCardKindT&quot;/> <xs:element name=&quot;cardNumber&quot; type=&quot;xs:string&quot;/> <xs:element name=&quot;cardholderFirstName&quot; type=&quot;xs:string&quot; minOccurs=&quot;0&quot;/> <xs:element name=&quot;cardholderLastName&quot; type=&quot;xs:string&quot;/> <xs:element name=&quot;expirationMonth&quot; type=&quot;tns:MonthT&quot;/> <xs:element name=&quot;expirationYear&quot; type=&quot;tns:YearT&quot;/> </xs:sequence> <xs:attribute name=&quot;id&quot; type=&quot;xs:int&quot;/> </xs:complexType> <xs:simpleType name=&quot;CreditCardKindT&quot;> <xs:restriction base=&quot;xs:string&quot;> <xs:enumeration value=&quot;visa&quot;/> <xs:enumeration value=&quot;mastercard&quot;/> <xs:enumeration value=&quot;amexco&quot;/> </xs:restriction> </xs:simpleType> ... /xs:schema>
Agenda Introduction Alternative ways to design service contract Domain Specific Languages (DSL) Eclipse Xtext Prototype Implementations Summary Using Domain Specific Language (s) to Simplify Creating SOA Artifacts Data are always part of the game.
WSDL and XSD UML Profile in UML Tools Enterprise Architect has a special profile for WSDL and XSD modelling Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
CBDI-SAE Meta Model for SOA The CBDI-SAE Meta Model for SOA is a 'class model' of the concepts contained in the CBDI Service Architecture & Engineering TM (CBDI-SAE TM ) Reference Framework.  CBDI-SAE Meta Model for SOA, which is realized via the CBDI-SAE UML Profile for SOA Which is compliant with SoaML -  for which also a SoaML Profile exists. http://everware-cbdi.com Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
CBDI-SAE UML Profile for SOA Using Domain Specific Language (s) to Simplify Creating SOA Artifacts Business Type Model Showing Domains Service Implementation Architecture Showing Services and Automation Units Service Deloyment Architecture Showing Deployments http://everware-cbdi.com
SoaML An OMG Standard for Modeling Service Oriented Architectures Adopted from the UML ® Profile for Modeling Services (UPMS) RFP Used for modeling SOA at the business, enterprise and technology levels Leverages Model Driven Architecture A “Profile” of the Unified Modeling Language™ Can be used with off-the-shelf UML tools as well as customized tooling In the “finalization” stage of the OMG process – essentially an adopted “beta” specification Finalization with minor clean-up expected to complete this year Tool support & implementations already exist Tool support – making it easy to create services models MDA Implementations – provisioning web services, business artifacts and implementations from SoaML models Using Domain Specific Language (s) to Simplify Creating SOA Artifacts 1.0-Beta-2 available: http://www.omg.org/spec/SoaML/
SoaML - Goals Intuitive and complete support for modeling services in UML Support for bi-directional asynchronous services between multiple parties Support for Services Architectures where parties provide and use multiple services. Easily mapped to and made part of a business process specification Compatibility with UML, BPDM and BPMN for business processes Direct mapping to web services Top-down, bottom up or meet-in-the-middle modeling Design by contract or dynamic adaptation of services To specify and relate the service capability and its contract No changes to UML Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
SoaML Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
MDA vs. MDSD MDA = Model Driven Architecture 100% generation Standardized by the OMG since 1999 Based on XMI, MOC, OCL, UML... Aims at automating all transformations between models to code , suppressing the coding part Driven by CIMs, PIMs, PSMs and PDMs Tries to define standard meta-models shared across industry domains MDSD = Model Driven Software Development Based on the ideas brought by MDA Not bound to its standards can be any meta-model like DSLs, not only UML and profiles Try to promote customized DSLs, not assuming that every body will have the same needs on a given domain Use models as abstraction and still leave a place for development tasks Defines its own ideas of PIMs and PDMs depending on projects or needs contexts Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
MDA vs. MDSD MDA standard is more something made for the big players in the industry MDSD is a more flexible approach that can be used by a larger group of users, less attached to standards and with smaller scale needs. MDSD is a pragmatic way of using MDA concepts MDSD is more lightweight than MDA Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
But wouldn't it be easier .... use a DSL for WSDL Using Domain Specific Language (s) to Simplify Creating SOA Artifacts <wsdl:definitions xmlns:tns=&quot;http://trivadis.com/service/credit-card/v1&quot; ... name=&quot;CreditCardValidation-v1&quot;> <wsdl:types> <xsd:schema ...> </wsdl:types> <wsdl:message name=&quot;validateCardRequest&quot;> <wsdl:part name=&quot;request&quot; element=&quot;tns:validateCreditCardPaymentRequest&quot;/> </wsdl:message> <wsdl:message name=&quot;validateCardResponse&quot;> <wsdl:part name=&quot;reply&quot; element=&quot;tns:validateCreditCardPaymentResponse&quot;/> </wsdl:message> <wsdl:message name=&quot;invalidCreditCardNumberFault&quot;> <wsdl:part name=&quot;error„ element=&quot;tns:invalidCreditCardNumberFault&quot;/> </wsdl:message> <wsdl:portType name=&quot;CreditCardValidationPT&quot;> <wsdl:operation name=&quot;validateCard&quot;> <wsdl:input message=&quot;tns:validateCardRequest&quot;/> <wsdl:output message=&quot;tns:validateCardResponse&quot;/> <wsdl:fault name=&quot;InvalidCreditCardNumberFault&quot; message=&quot;tns:invalidCreditCardNumberFault&quot;/> </wsdl:operation> </wsdl:portType> <wsdl:binding ...> <wsdl:service ...> </wsdl:definitions> abstract message common { requestNr : String [1:1] } Import common.msgtype namespace service.credit-card(1.0) using cdm.credit-card(1.0) as cc message validateCardRequest extends common { creditCard : cc.CreditCard forAmount : Double } message validateCardResponse { requestNr : String[1:1] reservationNumber : String } fault invalidCreditCardNumber { code : String creditCard : cc.CreditCard } service CreditCardValidation { sync operation validateCard throws invalidCreditCardNumber input validateCardRequest output validateCardResponse }
... and for the XSD‘s .... Using Domain Specific Language (s) to Simplify Creating SOA Artifacts namespace cdm.credit-card(1.0) entity CreditCard { id : Integer creditCardKind : CreditCardKind [1:1] cardNumber : String [1:1] cardholderFirstName : String cardholderLastName : String [1:1] expirationMonth : Month [1:1] expirationYear : Year [1:1] } dataType Month extends Integer pattern &quot;[0-1][0-9]&quot; dataType Year extends Integer pattern &quot;[0-9][0-9][0-9][0-9]&quot; dataType CrediCardKind extends String enum { &quot;visa&quot;, &quot;mastercard&quot;, &quot;amexco&quot; } <xs:schema xmlns:xs=„...&quot; xmlns:tns=&quot;http://www.trivadis.com/cdm/credit-card/v1&quot; targetNamespace= „http://www.trivadis.com/cdm/credit-card/v1 “ elementFormDefault=&quot;qualified&quot; attributeFormDefault=&quot;unqualified&quot; version=&quot;1.0&quot;> <xs:element name=&quot;creditCard&quot; type=&quot;tns:CreditCardT&quot;/> <xs:complexType name=&quot;CreditCardT&quot;> <xs:sequence> <xs:element name=&quot;creditCardKind&quot; type=&quot;tns:CreditCardKindT&quot;/> <xs:element name=&quot;cardNumber&quot; type=&quot;xs:string&quot;/> <xs:element name=&quot;cardholderFirstName&quot; type=&quot;xs:string&quot; minOccurs=&quot;0&quot;/> <xs:element name=&quot;cardholderLastName&quot; type=&quot;xs:string&quot;/> <xs:element name=&quot;expirationMonth&quot; type=&quot;tns:MonthT&quot;/> <xs:element name=&quot;expirationYear&quot; type=&quot;tns:YearT&quot;/> </xs:sequence> <xs:attribute name=&quot;id&quot; type=&quot;xs:int&quot;/> </xs:complexType> <xs:simpleType name=&quot;CreditCardKindT&quot;> <xs:restriction base=&quot;xs:string&quot;> <xs:enumeration value=&quot;visa&quot;/> <xs:enumeration value=&quot;mastercard&quot;/> <xs:enumeration value=&quot;amexco&quot;/> </xs:restriction> </xs:simpleType> ... /xs:schema>
Agenda Introduction Alternative ways to design service contract Domain Specific Languages (DSL) Eclipse Xtext Prototype Implementations Summary Using Domain Specific Language (s) to Simplify Creating SOA Artifacts Data are always part of the game.
Domain Specific Language (DSL) A Domain Specific Language (DSL) is A small programming language, which focuses on a particular domain The right tool for the right job The opposite is a General Purpose Language (GPL) A language such as Java or C# A general purpose modeling language such as UML A DSL can be a visual diagramming, programatic abstractions or textual languages Text based DSL are more and more common Examples of existing DSL‘s SQL, Ant, XML, BPEL, BPMN Define you own custom DSL according to the problem Service interface in our case Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
Internal vs. External DSL Internal DSL The easiest form to write a DSL No need for grammer and language parsing Use regular language environment So any experssion must be a legal expression in the host language Influenced by Ruby, Groovy .... API's designed that expression look like DSL Fluent language, Method chaining External DSL analogous to creating a general purpose programming language Needs a formal grammar Often has a text format, but can be visual (graphical) as well parsing process operates on pure text input which is not constrained by any particular language Not immediately executable either an interpreter or generator is used Using Domain Specific Language (s) to Simplify Creating SOA Artifacts computer(&quot;A&quot;) .processor().cores(2).i386() .disk().size(150) .disk().size(75).speed(7200).sata() .end(); computer A { processor i386 with 2 cores disks { size 150 size 75 speed 7200 type sata } Processor p = new Processor(2, Processor.Type.i386); Disk d1 = new Disk(150, Disk.UNKNOWN_SIZE, null); Disk d2 = new Disk(75, 7200, Disk.Interface.SATA); return new Computer(p, d1, d2);
Domain Specific Language (DSL) Advantages allow solutions to be expressed at the level of abstraction of the problem domain so that domain experts themselves can understand, validate, modify, and often even develop DSL programs Self-documenting code DSL enhance quality, productivity, reliability, maintainability, portability and reusability DSL allow validation at the domain level Disadvantages Cost of learning a new language vs. its limited applicability Cost of designing, implementing, and maintaining a DSL as well as the tools required to develop with it (IDE) Finding, setting, and maintaining proper scope Difficulty of balancing trade-offs between domain-specificity and general-purpose programming language constructs Potential loss of processor efficiency compared with hand-coded software Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
Agenda Introduction Alternative ways to design service contract Domain Specific Languages (DSL) Eclipse Xtext Prototype Implementations Summary Using Domain Specific Language (s) to Simplify Creating SOA Artifacts Data are always part of the game.
What is Eclipse Xtext Language Development Framework / Domain Specific Language Framework Based on Eclipse Modeling Framework (EMF) ANTLR Parser Generator Google Guice Xtext is a professional Open-Source project the main developers and the project lead, work for itemis, a well known consulting company specialized on model-based development Xtext is an Eclipse.org project no IP issues, because the Eclipse Foundation has their own lawyers who take care that no intellectual property is violated. Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
Highlights of Xtext Xtext – Language Development Framework Syntax Highlighting Code Completion Validation and Quick Fixes More Editor Features Advanced Workbench Integration Integration with EMF Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
Xtext in Action Create an Xtext Project Build the Grammar Generate the Language Artefacts Run the Generated IDE Plug-in Write a Code Generator Using Domain Specific Language (s) to Simplify Creating SOA Artifacts DSL to be supported
Xtext in Action – 1. Create an Xtext Project Use the Xtext wizard to create a new project: File -> New -> Project... -> Xtext -> Xtext project Keep “Create generator project” checked we will use the code generator in a second step Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
Xtext in Action – 2. Build the Grammer Grammar has two purposes describes the concrete syntax of text files that can be processed by the tools of your new DSL equates the meta level, i.e. the model which describes your model A Grammar as a unique name Terminal rules / Parser rules Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
Xtext in Action – 2. Build the Grammer The DomainModel consists of elements An AbstractElement can either be a PackageDeclaration or a Type Boolean assignment operator ?= A QualifiedName is a sequence of IDs and dots Using Domain Specific Language (s) to Simplify Creating SOA Artifacts (no operator) exactly one ? zero or one * zero or more + one or more feature=... corresponds to setFeature(...) list+=... corresponds to getList().add(...) condition?=... corresponds to setCondition(true) DomainModel : (elements+=AbstractElement)*; AbstractElement: PackageDeclaration | Type; TypeRef: referenced=[Type] (multi?='*')?; QualifiedName: ID (‚.‘ ID)*;
Xtext in Action – 3. Generate Language Artefacts Now we need to run the generator that will derive the various language components. locate the file GenerateXtextDemo.mwe2 file next to the grammar file in the package explorer view from its context menu, choose Run As -> MWE2 Workflow Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
Xtext in Action – 4. Run the Generated IDE Plug-in Right-click on the Xtext project and choose Run As -> Eclipse Application In new workbench, create a new project ( File -> New -> Project... -> General -> Project) and therein a new file with the file extension you chose in the beginning ( *.xtextdemo). Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
Xtext in Action – 5. Write a Code Generator We checked the option Create a generator project in the wizard, which as a result created a third project for us in the workspace First let's change the workflow to call the template for Entity's Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
Xtext in Action – 5. Write a Code Generator Using Xpand and Xtend for Code generation Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
Xtext in Action – 5. Write a Code Generator Result generated Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
Agenda Introduction Alternative ways to design service contract Domain Specific Languages (DSL) Eclipse Xtext Prototype Implementation Summary Using Domain Specific Language (s) to Simplify Creating SOA Artifacts Data are always part of the game.
Service DSL Prototype Grammar DSL in action Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
Agenda Introduction Alternative ways to design service contract Domain Specific Languages (DSL) Eclipse Xtext Prototype Implementation Summary Using Domain Specific Language (s) to Simplify Creating SOA Artifacts Data are always part of the game.
Summary DSL can help to simplify creation of XSD’s and WSDL Eclipse Xtext offers very strong support for implementing DSL First prototype of DSL and Generator for WSDL and XSD is ready Still in proof-of-concept stage Grammar needs to be revised Some grammar and code refactoring necessary Advanced IDE functionalities like Quick Fix, Formatting, Templates have not yet been used Will be extended to generate more artifacts of a given SOA platform i.e. Oracle Service Bus (OSB) proxy services handling service versioning Support Testing Add governance information (consumer + producer information, service classification, domain, ownership, SLA, …) Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
Thank you! SOA Symposium 2010 Guido Schmutz, Technology Manager / Partner Trivadis AG 5.10.2010, Berlin

More Related Content

PPT
Ibm 1 Wps Arch
luohd
 
PDF
Dot net training bangalore
IGEEKS TECHNOLOGIES
 
PPS
XML Unit 01
Prashanth Shivakumar
 
PPS
Web Component Development with Servlet and JSP Technologies Unit 01
Prashanth Shivakumar
 
PDF
Silverlight 4
Supote Phunsakul
 
PPTX
Partying with PHP (…and the Microsoft Platform)
goodfriday
 
PPT
Flex in portal
Sunil Patil
 
PDF
Frontend APIs powering fast paced product iterations
Karthik Ramgopal
 
Ibm 1 Wps Arch
luohd
 
Dot net training bangalore
IGEEKS TECHNOLOGIES
 
XML Unit 01
Prashanth Shivakumar
 
Web Component Development with Servlet and JSP Technologies Unit 01
Prashanth Shivakumar
 
Silverlight 4
Supote Phunsakul
 
Partying with PHP (…and the Microsoft Platform)
goodfriday
 
Flex in portal
Sunil Patil
 
Frontend APIs powering fast paced product iterations
Karthik Ramgopal
 

Viewers also liked (10)

PPTX
de novo drug design
mojdeh y
 
PDF
Programming Without Coding Technology (PWCT) - Get Input From User
Mahmoud Samir Fayed
 
PDF
Programming Without Coding Technology (PWCT) - Radiogroup control
Mahmoud Samir Fayed
 
DOCX
خدمات ابنيات
abniyat4egypt
 
PDF
Programming Without Coding Technology (PWCT) - Image control
Mahmoud Samir Fayed
 
PDF
Sasaki Associates: Retrospective Pinup Opening Event
Sasaki Associates
 
PDF
ROUNDTABLE 2016: BERNARD
LEAP Media Solutions, a division of BlueVenn
 
PDF
VAVE certification
Rajkumar R
 
DOC
bio (3)
NEERAJ SHARDA
 
PPTX
SC12 S3700 Series launch event gold
Alan Frost
 
de novo drug design
mojdeh y
 
Programming Without Coding Technology (PWCT) - Get Input From User
Mahmoud Samir Fayed
 
Programming Without Coding Technology (PWCT) - Radiogroup control
Mahmoud Samir Fayed
 
خدمات ابنيات
abniyat4egypt
 
Programming Without Coding Technology (PWCT) - Image control
Mahmoud Samir Fayed
 
Sasaki Associates: Retrospective Pinup Opening Event
Sasaki Associates
 
ROUNDTABLE 2016: BERNARD
LEAP Media Solutions, a division of BlueVenn
 
VAVE certification
Rajkumar R
 
bio (3)
NEERAJ SHARDA
 
SC12 S3700 Series launch event gold
Alan Frost
 
Ad

Similar to Dsl for-soa-artefacts (20)

PPT
Build Message-Based Web Services for SOA
Jeffrey Hasan
 
PPTX
SQLSaturday #341 porto - Introduction to Microsoft Azure BizTalk Services
Sandro Pereira
 
PPTX
Global Windows Azure Bootcamp – Lisboa - Windows Azure Biztalk Services
Sandro Pereira
 
PPT
Open Source Soa
Arun Pareek
 
PDF
January 2017 - Deep dive on AWS Lambda and DevOps
David McDaniel
 
PPT
Building Applications for SQL Server 2008
Dave Bost
 
PDF
D2 domain driven-design
Arnaud Bouchez
 
PDF
AWS Chicago user group: AWS Platform for .NET Developers
AWS Chicago
 
PPT
Alchemy Publisher Presentation
Shamusd
 
PPTX
Mdd Lcds
ravinxg
 
PPTX
Mdd lcds
rssharma
 
PPS
Sioux Hot-or-Not: Model Driven Software Development (Markus Voelter)
siouxhotornot
 
PPT
Biztalk Server 2006
ipaciti
 
PPT
Innovate2011 Keys to Building OSLC Integrations
Steve Speicher
 
PPTX
FME World Tour 2015: (EN) FME 2015 in action
GIM_nv
 
PPT
Anatomy Of A Driver Presentation 09 15 2008
ctindale
 
PPT
MAX 2008: Build collaborative applications with Flex LCDS and Cairngorm
Xavier Agnetti
 
PPTX
2014 q3-platform-update-v1.06.johnmathon
aaronwso2
 
PPT
Contract First Modeling Services Using Uml
Rody Middelkoop
 
PPTX
Rapidly building data-driven modern Office 365 Cloud Business add-ins with Li...
Marius Constantinescu [MVP]
 
Build Message-Based Web Services for SOA
Jeffrey Hasan
 
SQLSaturday #341 porto - Introduction to Microsoft Azure BizTalk Services
Sandro Pereira
 
Global Windows Azure Bootcamp – Lisboa - Windows Azure Biztalk Services
Sandro Pereira
 
Open Source Soa
Arun Pareek
 
January 2017 - Deep dive on AWS Lambda and DevOps
David McDaniel
 
Building Applications for SQL Server 2008
Dave Bost
 
D2 domain driven-design
Arnaud Bouchez
 
AWS Chicago user group: AWS Platform for .NET Developers
AWS Chicago
 
Alchemy Publisher Presentation
Shamusd
 
Mdd Lcds
ravinxg
 
Mdd lcds
rssharma
 
Sioux Hot-or-Not: Model Driven Software Development (Markus Voelter)
siouxhotornot
 
Biztalk Server 2006
ipaciti
 
Innovate2011 Keys to Building OSLC Integrations
Steve Speicher
 
FME World Tour 2015: (EN) FME 2015 in action
GIM_nv
 
Anatomy Of A Driver Presentation 09 15 2008
ctindale
 
MAX 2008: Build collaborative applications with Flex LCDS and Cairngorm
Xavier Agnetti
 
2014 q3-platform-update-v1.06.johnmathon
aaronwso2
 
Contract First Modeling Services Using Uml
Rody Middelkoop
 
Rapidly building data-driven modern Office 365 Cloud Business add-ins with Li...
Marius Constantinescu [MVP]
 
Ad

More from Guido Schmutz (20)

PDF
30 Minutes to the Analytics Platform with Infrastructure as Code
Guido Schmutz
 
PDF
Event Broker (Kafka) in a Modern Data Architecture
Guido Schmutz
 
PDF
Big Data, Data Lake, Fast Data - Dataserialiation-Formats
Guido Schmutz
 
PDF
ksqlDB - Stream Processing simplified!
Guido Schmutz
 
PDF
Kafka as your Data Lake - is it Feasible?
Guido Schmutz
 
PDF
Event Hub (i.e. Kafka) in Modern Data Architecture
Guido Schmutz
 
PDF
Solutions for bi-directional integration between Oracle RDBMS & Apache Kafka
Guido Schmutz
 
PDF
Event Hub (i.e. Kafka) in Modern Data (Analytics) Architecture
Guido Schmutz
 
PDF
Building Event Driven (Micro)services with Apache Kafka
Guido Schmutz
 
PDF
Location Analytics - Real-Time Geofencing using Apache Kafka
Guido Schmutz
 
PDF
Solutions for bi-directional integration between Oracle RDBMS and Apache Kafka
Guido Schmutz
 
PDF
What is Apache Kafka? Why is it so popular? Should I use it?
Guido Schmutz
 
PDF
Solutions for bi-directional integration between Oracle RDBMS & Apache Kafka
Guido Schmutz
 
PDF
Location Analytics Real-Time Geofencing using Kafka
Guido Schmutz
 
PDF
Streaming Visualisation
Guido Schmutz
 
PDF
Kafka as an event store - is it good enough?
Guido Schmutz
 
PDF
Solutions for bi-directional Integration between Oracle RDMBS & Apache Kafka
Guido Schmutz
 
PDF
Fundamentals Big Data and AI Architecture
Guido Schmutz
 
PDF
Location Analytics - Real-Time Geofencing using Kafka
Guido Schmutz
 
PDF
Streaming Visualization
Guido Schmutz
 
30 Minutes to the Analytics Platform with Infrastructure as Code
Guido Schmutz
 
Event Broker (Kafka) in a Modern Data Architecture
Guido Schmutz
 
Big Data, Data Lake, Fast Data - Dataserialiation-Formats
Guido Schmutz
 
ksqlDB - Stream Processing simplified!
Guido Schmutz
 
Kafka as your Data Lake - is it Feasible?
Guido Schmutz
 
Event Hub (i.e. Kafka) in Modern Data Architecture
Guido Schmutz
 
Solutions for bi-directional integration between Oracle RDBMS & Apache Kafka
Guido Schmutz
 
Event Hub (i.e. Kafka) in Modern Data (Analytics) Architecture
Guido Schmutz
 
Building Event Driven (Micro)services with Apache Kafka
Guido Schmutz
 
Location Analytics - Real-Time Geofencing using Apache Kafka
Guido Schmutz
 
Solutions for bi-directional integration between Oracle RDBMS and Apache Kafka
Guido Schmutz
 
What is Apache Kafka? Why is it so popular? Should I use it?
Guido Schmutz
 
Solutions for bi-directional integration between Oracle RDBMS & Apache Kafka
Guido Schmutz
 
Location Analytics Real-Time Geofencing using Kafka
Guido Schmutz
 
Streaming Visualisation
Guido Schmutz
 
Kafka as an event store - is it good enough?
Guido Schmutz
 
Solutions for bi-directional Integration between Oracle RDMBS & Apache Kafka
Guido Schmutz
 
Fundamentals Big Data and AI Architecture
Guido Schmutz
 
Location Analytics - Real-Time Geofencing using Kafka
Guido Schmutz
 
Streaming Visualization
Guido Schmutz
 

Recently uploaded (20)

PDF
MIND Revenue Release Quarter 2 2025 Press Release
MIND CTI
 
PPTX
Big Data Technologies - Introduction.pptx
kuthubussaman1
 
PDF
Approach and Philosophy of On baking technology
30anthuong17
 
PDF
Accuracy of neural networks in brain wave diagnosis of schizophrenia
IAESIJAI
 
PDF
Unlocking AI with Model Context Protocol (MCP)
Brian McKeiver
 
PDF
TokAI - TikTok AI Agent : The First AI Application That Analyzes 10,000+ Vira...
SOFTTECHHUB
 
PPTX
Machine Learning_overview_presentation.pptx
kondavamsidharreddy2
 
PPTX
1. Introduction to Computer Programming.pptx
bonakiduza1024
 
PDF
Agricultural_Statistics_at_a_Glance_2022_0.pdf
SandeepSingh286037
 
PDF
Encapsulation theory and applications.pdf
gurumoop
 
PDF
Architecting across the Boundaries of two Complex Domains - Healthcare & Tech...
Peter Tan
 
PPTX
20250228 LYD VKU AI Blended-Learning.pptx
DatVoNgoc
 
PPTX
SOPHOS-XG Firewall Administrator PPT.pptx
AgnesMunisi
 
PDF
Per capita expenditure prediction using model stacking based on satellite ima...
IAESIJAI
 
PDF
Getting Started with Data Integration: FME Form 101
Safe Software
 
PDF
Reach Out and Touch Someone: Haptics and Empathic Computing
Mark Billinghurst
 
PDF
Profit Center Accounting in SAP S/4HANA, S4F28 Col11
Libreria ERP
 
PDF
Assigned Numbers - 2025 - Bluetooth® Document
Bloombase
 
PDF
Machine learning based COVID-19 study performance prediction
IAESIJAI
 
PPTX
Tartificialntelligence_presentation.pptx
ry7r52mzb4
 
MIND Revenue Release Quarter 2 2025 Press Release
MIND CTI
 
Big Data Technologies - Introduction.pptx
kuthubussaman1
 
Approach and Philosophy of On baking technology
30anthuong17
 
Accuracy of neural networks in brain wave diagnosis of schizophrenia
IAESIJAI
 
Unlocking AI with Model Context Protocol (MCP)
Brian McKeiver
 
TokAI - TikTok AI Agent : The First AI Application That Analyzes 10,000+ Vira...
SOFTTECHHUB
 
Machine Learning_overview_presentation.pptx
kondavamsidharreddy2
 
1. Introduction to Computer Programming.pptx
bonakiduza1024
 
Agricultural_Statistics_at_a_Glance_2022_0.pdf
SandeepSingh286037
 
Encapsulation theory and applications.pdf
gurumoop
 
Architecting across the Boundaries of two Complex Domains - Healthcare & Tech...
Peter Tan
 
20250228 LYD VKU AI Blended-Learning.pptx
DatVoNgoc
 
SOPHOS-XG Firewall Administrator PPT.pptx
AgnesMunisi
 
Per capita expenditure prediction using model stacking based on satellite ima...
IAESIJAI
 
Getting Started with Data Integration: FME Form 101
Safe Software
 
Reach Out and Touch Someone: Haptics and Empathic Computing
Mark Billinghurst
 
Profit Center Accounting in SAP S/4HANA, S4F28 Col11
Libreria ERP
 
Assigned Numbers - 2025 - Bluetooth® Document
Bloombase
 
Machine learning based COVID-19 study performance prediction
IAESIJAI
 
Tartificialntelligence_presentation.pptx
ry7r52mzb4
 

Dsl for-soa-artefacts

  • 1. Using Domain Specific Language(s) to Simplify Creating SOA Artifacts SOA Symposium 2010 Guido Schmutz, Technology Manager / Partner Trivadis AG 5.10.2010, Berlin
  • 2. Introduction Guido Schmutz Working for Trivadis for more than 13 years leading and independent IT service company operating in Germany, Austria and Switzerland Oracle ACE Director for Fusion Middleware and SOA Co-Author of different books Consultant, Trainer Software Architect for Java, Oracle, SOA and EDA More than 20 years of software development experience Contact: [email_address] Blog: http://guidoschmutz.wordpress.com/ Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 3. About Trivadis Swiss IT consulting company 13 locations in Switzerland, Germany and Austria ~ 540 employees Key figures 2009 Services for more than 650 clients in over 1'600 projects Over 150 service level agreements More than 5'000 training participants Research and development budget: CHF 6.0 Mio. / EUR 3.6 Mio.
  • 4. Agenda Introduction Alternative ways to design service contract Domain Specific Languages (DSL) Eclipse Xtext Prototype Implementations Summary Using Domain Specific Language (s) to Simplify Creating SOA Artifacts Data are always part of the game.
  • 5. „ Problem“ Most SOA platforms do not make a contract-first service design easy Creation of WSDL and XSD is too much effort There is build-in support in the IDE to graphically implement WSDL and XSD Platform specific, no standard for look-and-feel Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 6. „ Problem“ Lot of repetition Very talkative More options than (often) necessary => RPC/literal How to ensure Design guidelines WS-I compliance Asynchronous Interface Service versioning Ensure naming conventions Name of messages Name of port types Name of bindings So what are the other options? Using Domain Specific Language (s) to Simplify Creating SOA Artifacts <wsdl:definitions xmlns:tns=&quot;http://trivadis.com/service/credit-card/v1&quot; ... name=&quot;CreditCardValidation-v1&quot;> <wsdl:types> <xsd:schema ...> </wsdl:types> <wsdl:message name=&quot;validateCardRequest&quot;> <wsdl:part name=&quot;request&quot; element=&quot;tns:validateCreditCardPaymentRequest&quot;/> </wsdl:message> <wsdl:message name=&quot;validateCardResponse&quot;> <wsdl:part name=&quot;reply&quot; element=&quot;tns:validateCreditCardPaymentResponse&quot;/> </wsdl:message> <wsdl:message name=&quot;invalidCreditCardNumberFault&quot;> <wsdl:part name=&quot;error„ element=&quot;tns:invalidCreditCardNumberFault&quot;/> </wsdl:message> <wsdl:portType name=&quot;CreditCardValidationPT&quot;> <wsdl:operation name=&quot;validateCard&quot;> <wsdl:input message=&quot;tns:validateCardRequest&quot;/> <wsdl:output message=&quot;tns:validateCardResponse&quot;/> <wsdl:fault name=&quot;InvalidCreditCardNumberFault&quot; message=&quot;tns:invalidCreditCardNumberFault&quot;/> </wsdl:operation> </wsdl:portType> <wsdl:binding ...> <wsdl:service ...> </wsdl:definitions> <xs:schema xmlns:xs=„...&quot; xmlns:tns=&quot;http://www.trivadis.com/cdm/credit-card/v1&quot; targetNamespace= „http://www.trivadis.com/cdm/credit-card/v1 “ elementFormDefault=&quot;qualified&quot; attributeFormDefault=&quot;unqualified&quot; version=&quot;1.0&quot;> <xs:element name=&quot;creditCard&quot; type=&quot;tns:CreditCardT&quot;/> <xs:complexType name=&quot;CreditCardT&quot;> <xs:sequence> <xs:element name=&quot;creditCardKind&quot; type=&quot;tns:CreditCardKindT&quot;/> <xs:element name=&quot;cardNumber&quot; type=&quot;xs:string&quot;/> <xs:element name=&quot;cardholderFirstName&quot; type=&quot;xs:string&quot; minOccurs=&quot;0&quot;/> <xs:element name=&quot;cardholderLastName&quot; type=&quot;xs:string&quot;/> <xs:element name=&quot;expirationMonth&quot; type=&quot;tns:MonthT&quot;/> <xs:element name=&quot;expirationYear&quot; type=&quot;tns:YearT&quot;/> </xs:sequence> <xs:attribute name=&quot;id&quot; type=&quot;xs:int&quot;/> </xs:complexType> <xs:simpleType name=&quot;CreditCardKindT&quot;> <xs:restriction base=&quot;xs:string&quot;> <xs:enumeration value=&quot;visa&quot;/> <xs:enumeration value=&quot;mastercard&quot;/> <xs:enumeration value=&quot;amexco&quot;/> </xs:restriction> </xs:simpleType> ... /xs:schema>
  • 7. Agenda Introduction Alternative ways to design service contract Domain Specific Languages (DSL) Eclipse Xtext Prototype Implementations Summary Using Domain Specific Language (s) to Simplify Creating SOA Artifacts Data are always part of the game.
  • 8. WSDL and XSD UML Profile in UML Tools Enterprise Architect has a special profile for WSDL and XSD modelling Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 9. CBDI-SAE Meta Model for SOA The CBDI-SAE Meta Model for SOA is a 'class model' of the concepts contained in the CBDI Service Architecture & Engineering TM (CBDI-SAE TM ) Reference Framework.  CBDI-SAE Meta Model for SOA, which is realized via the CBDI-SAE UML Profile for SOA Which is compliant with SoaML -  for which also a SoaML Profile exists. http://everware-cbdi.com Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 10. CBDI-SAE UML Profile for SOA Using Domain Specific Language (s) to Simplify Creating SOA Artifacts Business Type Model Showing Domains Service Implementation Architecture Showing Services and Automation Units Service Deloyment Architecture Showing Deployments http://everware-cbdi.com
  • 11. SoaML An OMG Standard for Modeling Service Oriented Architectures Adopted from the UML ® Profile for Modeling Services (UPMS) RFP Used for modeling SOA at the business, enterprise and technology levels Leverages Model Driven Architecture A “Profile” of the Unified Modeling Language™ Can be used with off-the-shelf UML tools as well as customized tooling In the “finalization” stage of the OMG process – essentially an adopted “beta” specification Finalization with minor clean-up expected to complete this year Tool support & implementations already exist Tool support – making it easy to create services models MDA Implementations – provisioning web services, business artifacts and implementations from SoaML models Using Domain Specific Language (s) to Simplify Creating SOA Artifacts 1.0-Beta-2 available: http://www.omg.org/spec/SoaML/
  • 12. SoaML - Goals Intuitive and complete support for modeling services in UML Support for bi-directional asynchronous services between multiple parties Support for Services Architectures where parties provide and use multiple services. Easily mapped to and made part of a business process specification Compatibility with UML, BPDM and BPMN for business processes Direct mapping to web services Top-down, bottom up or meet-in-the-middle modeling Design by contract or dynamic adaptation of services To specify and relate the service capability and its contract No changes to UML Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 13. SoaML Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 14. MDA vs. MDSD MDA = Model Driven Architecture 100% generation Standardized by the OMG since 1999 Based on XMI, MOC, OCL, UML... Aims at automating all transformations between models to code , suppressing the coding part Driven by CIMs, PIMs, PSMs and PDMs Tries to define standard meta-models shared across industry domains MDSD = Model Driven Software Development Based on the ideas brought by MDA Not bound to its standards can be any meta-model like DSLs, not only UML and profiles Try to promote customized DSLs, not assuming that every body will have the same needs on a given domain Use models as abstraction and still leave a place for development tasks Defines its own ideas of PIMs and PDMs depending on projects or needs contexts Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 15. MDA vs. MDSD MDA standard is more something made for the big players in the industry MDSD is a more flexible approach that can be used by a larger group of users, less attached to standards and with smaller scale needs. MDSD is a pragmatic way of using MDA concepts MDSD is more lightweight than MDA Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 16. But wouldn't it be easier .... use a DSL for WSDL Using Domain Specific Language (s) to Simplify Creating SOA Artifacts <wsdl:definitions xmlns:tns=&quot;http://trivadis.com/service/credit-card/v1&quot; ... name=&quot;CreditCardValidation-v1&quot;> <wsdl:types> <xsd:schema ...> </wsdl:types> <wsdl:message name=&quot;validateCardRequest&quot;> <wsdl:part name=&quot;request&quot; element=&quot;tns:validateCreditCardPaymentRequest&quot;/> </wsdl:message> <wsdl:message name=&quot;validateCardResponse&quot;> <wsdl:part name=&quot;reply&quot; element=&quot;tns:validateCreditCardPaymentResponse&quot;/> </wsdl:message> <wsdl:message name=&quot;invalidCreditCardNumberFault&quot;> <wsdl:part name=&quot;error„ element=&quot;tns:invalidCreditCardNumberFault&quot;/> </wsdl:message> <wsdl:portType name=&quot;CreditCardValidationPT&quot;> <wsdl:operation name=&quot;validateCard&quot;> <wsdl:input message=&quot;tns:validateCardRequest&quot;/> <wsdl:output message=&quot;tns:validateCardResponse&quot;/> <wsdl:fault name=&quot;InvalidCreditCardNumberFault&quot; message=&quot;tns:invalidCreditCardNumberFault&quot;/> </wsdl:operation> </wsdl:portType> <wsdl:binding ...> <wsdl:service ...> </wsdl:definitions> abstract message common { requestNr : String [1:1] } Import common.msgtype namespace service.credit-card(1.0) using cdm.credit-card(1.0) as cc message validateCardRequest extends common { creditCard : cc.CreditCard forAmount : Double } message validateCardResponse { requestNr : String[1:1] reservationNumber : String } fault invalidCreditCardNumber { code : String creditCard : cc.CreditCard } service CreditCardValidation { sync operation validateCard throws invalidCreditCardNumber input validateCardRequest output validateCardResponse }
  • 17. ... and for the XSD‘s .... Using Domain Specific Language (s) to Simplify Creating SOA Artifacts namespace cdm.credit-card(1.0) entity CreditCard { id : Integer creditCardKind : CreditCardKind [1:1] cardNumber : String [1:1] cardholderFirstName : String cardholderLastName : String [1:1] expirationMonth : Month [1:1] expirationYear : Year [1:1] } dataType Month extends Integer pattern &quot;[0-1][0-9]&quot; dataType Year extends Integer pattern &quot;[0-9][0-9][0-9][0-9]&quot; dataType CrediCardKind extends String enum { &quot;visa&quot;, &quot;mastercard&quot;, &quot;amexco&quot; } <xs:schema xmlns:xs=„...&quot; xmlns:tns=&quot;http://www.trivadis.com/cdm/credit-card/v1&quot; targetNamespace= „http://www.trivadis.com/cdm/credit-card/v1 “ elementFormDefault=&quot;qualified&quot; attributeFormDefault=&quot;unqualified&quot; version=&quot;1.0&quot;> <xs:element name=&quot;creditCard&quot; type=&quot;tns:CreditCardT&quot;/> <xs:complexType name=&quot;CreditCardT&quot;> <xs:sequence> <xs:element name=&quot;creditCardKind&quot; type=&quot;tns:CreditCardKindT&quot;/> <xs:element name=&quot;cardNumber&quot; type=&quot;xs:string&quot;/> <xs:element name=&quot;cardholderFirstName&quot; type=&quot;xs:string&quot; minOccurs=&quot;0&quot;/> <xs:element name=&quot;cardholderLastName&quot; type=&quot;xs:string&quot;/> <xs:element name=&quot;expirationMonth&quot; type=&quot;tns:MonthT&quot;/> <xs:element name=&quot;expirationYear&quot; type=&quot;tns:YearT&quot;/> </xs:sequence> <xs:attribute name=&quot;id&quot; type=&quot;xs:int&quot;/> </xs:complexType> <xs:simpleType name=&quot;CreditCardKindT&quot;> <xs:restriction base=&quot;xs:string&quot;> <xs:enumeration value=&quot;visa&quot;/> <xs:enumeration value=&quot;mastercard&quot;/> <xs:enumeration value=&quot;amexco&quot;/> </xs:restriction> </xs:simpleType> ... /xs:schema>
  • 18. Agenda Introduction Alternative ways to design service contract Domain Specific Languages (DSL) Eclipse Xtext Prototype Implementations Summary Using Domain Specific Language (s) to Simplify Creating SOA Artifacts Data are always part of the game.
  • 19. Domain Specific Language (DSL) A Domain Specific Language (DSL) is A small programming language, which focuses on a particular domain The right tool for the right job The opposite is a General Purpose Language (GPL) A language such as Java or C# A general purpose modeling language such as UML A DSL can be a visual diagramming, programatic abstractions or textual languages Text based DSL are more and more common Examples of existing DSL‘s SQL, Ant, XML, BPEL, BPMN Define you own custom DSL according to the problem Service interface in our case Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 20. Internal vs. External DSL Internal DSL The easiest form to write a DSL No need for grammer and language parsing Use regular language environment So any experssion must be a legal expression in the host language Influenced by Ruby, Groovy .... API's designed that expression look like DSL Fluent language, Method chaining External DSL analogous to creating a general purpose programming language Needs a formal grammar Often has a text format, but can be visual (graphical) as well parsing process operates on pure text input which is not constrained by any particular language Not immediately executable either an interpreter or generator is used Using Domain Specific Language (s) to Simplify Creating SOA Artifacts computer(&quot;A&quot;) .processor().cores(2).i386() .disk().size(150) .disk().size(75).speed(7200).sata() .end(); computer A { processor i386 with 2 cores disks { size 150 size 75 speed 7200 type sata } Processor p = new Processor(2, Processor.Type.i386); Disk d1 = new Disk(150, Disk.UNKNOWN_SIZE, null); Disk d2 = new Disk(75, 7200, Disk.Interface.SATA); return new Computer(p, d1, d2);
  • 21. Domain Specific Language (DSL) Advantages allow solutions to be expressed at the level of abstraction of the problem domain so that domain experts themselves can understand, validate, modify, and often even develop DSL programs Self-documenting code DSL enhance quality, productivity, reliability, maintainability, portability and reusability DSL allow validation at the domain level Disadvantages Cost of learning a new language vs. its limited applicability Cost of designing, implementing, and maintaining a DSL as well as the tools required to develop with it (IDE) Finding, setting, and maintaining proper scope Difficulty of balancing trade-offs between domain-specificity and general-purpose programming language constructs Potential loss of processor efficiency compared with hand-coded software Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 22. Agenda Introduction Alternative ways to design service contract Domain Specific Languages (DSL) Eclipse Xtext Prototype Implementations Summary Using Domain Specific Language (s) to Simplify Creating SOA Artifacts Data are always part of the game.
  • 23. What is Eclipse Xtext Language Development Framework / Domain Specific Language Framework Based on Eclipse Modeling Framework (EMF) ANTLR Parser Generator Google Guice Xtext is a professional Open-Source project the main developers and the project lead, work for itemis, a well known consulting company specialized on model-based development Xtext is an Eclipse.org project no IP issues, because the Eclipse Foundation has their own lawyers who take care that no intellectual property is violated. Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 24. Highlights of Xtext Xtext – Language Development Framework Syntax Highlighting Code Completion Validation and Quick Fixes More Editor Features Advanced Workbench Integration Integration with EMF Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 25. Xtext in Action Create an Xtext Project Build the Grammar Generate the Language Artefacts Run the Generated IDE Plug-in Write a Code Generator Using Domain Specific Language (s) to Simplify Creating SOA Artifacts DSL to be supported
  • 26. Xtext in Action – 1. Create an Xtext Project Use the Xtext wizard to create a new project: File -> New -> Project... -> Xtext -> Xtext project Keep “Create generator project” checked we will use the code generator in a second step Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 27. Xtext in Action – 2. Build the Grammer Grammar has two purposes describes the concrete syntax of text files that can be processed by the tools of your new DSL equates the meta level, i.e. the model which describes your model A Grammar as a unique name Terminal rules / Parser rules Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 28. Xtext in Action – 2. Build the Grammer The DomainModel consists of elements An AbstractElement can either be a PackageDeclaration or a Type Boolean assignment operator ?= A QualifiedName is a sequence of IDs and dots Using Domain Specific Language (s) to Simplify Creating SOA Artifacts (no operator) exactly one ? zero or one * zero or more + one or more feature=... corresponds to setFeature(...) list+=... corresponds to getList().add(...) condition?=... corresponds to setCondition(true) DomainModel : (elements+=AbstractElement)*; AbstractElement: PackageDeclaration | Type; TypeRef: referenced=[Type] (multi?='*')?; QualifiedName: ID (‚.‘ ID)*;
  • 29. Xtext in Action – 3. Generate Language Artefacts Now we need to run the generator that will derive the various language components. locate the file GenerateXtextDemo.mwe2 file next to the grammar file in the package explorer view from its context menu, choose Run As -> MWE2 Workflow Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 30. Xtext in Action – 4. Run the Generated IDE Plug-in Right-click on the Xtext project and choose Run As -> Eclipse Application In new workbench, create a new project ( File -> New -> Project... -> General -> Project) and therein a new file with the file extension you chose in the beginning ( *.xtextdemo). Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 31. Xtext in Action – 5. Write a Code Generator We checked the option Create a generator project in the wizard, which as a result created a third project for us in the workspace First let's change the workflow to call the template for Entity's Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 32. Xtext in Action – 5. Write a Code Generator Using Xpand and Xtend for Code generation Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 33. Xtext in Action – 5. Write a Code Generator Result generated Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 34. Agenda Introduction Alternative ways to design service contract Domain Specific Languages (DSL) Eclipse Xtext Prototype Implementation Summary Using Domain Specific Language (s) to Simplify Creating SOA Artifacts Data are always part of the game.
  • 35. Service DSL Prototype Grammar DSL in action Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 36. Agenda Introduction Alternative ways to design service contract Domain Specific Languages (DSL) Eclipse Xtext Prototype Implementation Summary Using Domain Specific Language (s) to Simplify Creating SOA Artifacts Data are always part of the game.
  • 37. Summary DSL can help to simplify creation of XSD’s and WSDL Eclipse Xtext offers very strong support for implementing DSL First prototype of DSL and Generator for WSDL and XSD is ready Still in proof-of-concept stage Grammar needs to be revised Some grammar and code refactoring necessary Advanced IDE functionalities like Quick Fix, Formatting, Templates have not yet been used Will be extended to generate more artifacts of a given SOA platform i.e. Oracle Service Bus (OSB) proxy services handling service versioning Support Testing Add governance information (consumer + producer information, service classification, domain, ownership, SLA, …) Using Domain Specific Language (s) to Simplify Creating SOA Artifacts
  • 38. Thank you! SOA Symposium 2010 Guido Schmutz, Technology Manager / Partner Trivadis AG 5.10.2010, Berlin

Editor's Notes

  • #4: Hier könnte eine Kopfzeile stehen 06.10.10 Hier könnte eine Fusszeile stehen Ihr müsst nicht alle Punkt aufzählen. Vielleicht der Hinweis, CH-Unternehmen mit 13 Standorten in D-A-CH, Anzahl Mitarbeiter und das wir finanziell unabhängig sind.