Domain Specific Languages (EclipseCon 2012)
•Descargar como KEY, PDF•
0 recomendaciones•735 vistas
A presentation on domain
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Similar a Domain Specific Languages (EclipseCon 2012)
Similar a Domain Specific Languages (EclipseCon 2012) (20)
Más de Sven Efftinge
Más de Sven Efftinge (20)
Último
Último (20)
Domain Specific Languages (EclipseCon 2012)
- 1. DOMAIN-SPECIFIC LANGUAGES @svenefftinge
- 2. DOMAIN-SPECIFIC LANGUAGE A Domain Specific Language (DSL) is a computer programming language focused on a particular domain.
- 3. DOMAIN-SPECIFIC LANGUAGE Or just a hip term for a very readable and expressive programming interface (aka API)
- 4. IT IS NOT! A WAY TO LET BUSINESS PEOPLE WRITE SOFTWARE
- 5. ABSTRACTION "THE ABILITY TO SIMPLIFY MEANS TO ELIMINATE THE UNNECESSARY SO THAT THE NECESSARY MAY SPEAK" (HANS HOFMANN)
- 6. A TYPICAL WEB APPLICATION Request Response
- 7. A TYPICAL WEB APPLICATION
- 8. A TYPICAL WEB APPLICATION Http Routing
- 9. A TYPICAL WEB APPLICATION Http Routing Controller
- 10. A TYPICAL WEB APPLICATION Http Routing Controller Domain Model
- 11. A TYPICAL WEB APPLICATION Http Routing Controller Domain Model Data Access
- 12. A TYPICAL WEB APPLICATION Http Routing Controller Domain Model Templates for HTML, CSS and JS Data Access
- 13. A TYPICAL WEB APPLICATION ? Http Routing ? Controller ? Domain Model ? Templates for HTML, CSS and JS ? Data Access
- 14. Http Routing
- 16. HTTP-ROUTING WITH SERVLET API
- 17. Java / Xtend
- 18. HTTP-ROUTING WITH JAX-RS Java / Xtend
- 20. HTTP-ROUTING WITH PLAY!
- 21. HTTP-ROUTING WITH PLAY! Static Typing ?
- 22. HTTP-ROUTING WITH PLAY! Static Typing ? Viewpoint Specific Analysis?
- 23. A TYPICAL WEB APPLICATION Http Routing ? Controller ? Domain Model ? Templates for HTML, CSS and JS ? Data Access
- 24. Controller
- 25. Controller Use a General Purpose Language: Java, ..., Xtend, ...
- 26. A TYPICAL WEB APPLICATION Http Routing Controller ? Domain Model ? Templates for HTML, CSS and JS ? Data Access
- 27. Templates for HTML, CSS and JS
- 29. <%@ page language="java" import="captchas.CaptchasDotNet" %> <html> <head> </head> Java Server Pages <title>Sample JSP CAPTCHA Query</title> <h1>Sample JSP CAPTCHA Query</h1> Velocity <% CaptchasDotNet captchas = new captchas.CaptchasDotNet( request.getSession(true), // Ensure session "demo", // client Freemarker "secret" // secret );%> <form method="get" action="<%=response.encodeUrl("check.jsp")%>"> Hamlets <table> <tr> <td><input name="message" size="60" /> Scalate </tr> <tr> <td> <input name="password" size="16" /> </td> </tr> <tr> StringTemplate <td> Thymeleaf <%= captchas.image() %><br> <a href="<%= captchas.audioUrl() %>">Phonetic spelling (mp3)</a> Jamon </td> </tr> <tr> WebMacro <td> <input type="submit" value="Submit" /> </td> </tr> </table> </form> </html> ...
- 30. html [ head [ title [$("XML encoding with Xtend")] ] body [ h1 [$("XML encoding with Xtend")] p [$("this format can be used as an alternative to XML")] // an element with attributes and text content a("http://www.xtend-lang.org") [$("Xtend")] // mixed content p [ $("This is some") b[$("mixed")] $("text. For more see the") a("http://www.xtext.org")[$("Xtext")] $("project") ] p [$("some text")] // content generated from arguments p [ for (arg : args) $(arg) ] ] ]
- 31. A TYPICAL WEB APPLICATION Http Routing Controller ? Domain Model Templates for HTML, CSS and JS ? Data Access
- 32. Data Access
- 33. DATA ACCESS WITH JPA QUERY LANGUAGE
- 34. .NET LINQ val namesWithFiveCharacters = from name in names where name.Length < 5 select name;
- 35. SCALA QUERY val q1 = for(u <- Users if u.first === "Stefan") yield u.id ~ u.last
- 36. A TYPICAL WEB APPLICATION Http Routing Controller ? Domain Model Templates for HTML, CSS and JS Data Access
- 37. Domain Model
- 39. @Entity public class Customer implements Serializable { private Long id; private String name; private Address address; private Collection<Order> orders = new HashSet<Order>(); private Set<PhoneNumber> phones = new HashSet<PhoneNumber>(); public Customer() {} @Id public Long getId() { return id; } public void setId(Long id) { this.id = id; } public String getName() { return name; } public void setName(String name) { this.name = name; } public Address getAddress() { return address; } public void setAddress(Address address) { this.address = address; } @OneToMany public Collection<Order> getOrders() { return orders; } public void setOrders(Collection<Order> orders) { this.orders = orders; } @ManyToMany public Set<PhoneNumber> getPhones() { return phones; } public void setPhones(Set<PhoneNumber> phones) { this.phones = phones; } }
- 40. ABSTRACTION "THE ABILITY TO SIMPLIFY MEANS TO ELIMINATE THE UNNECESSARY SO THAT THE NECESSARY MAY SPEAK" (HANS HOFMANN)
- 41. @Entity public class Customer implements Serializable { private Long id; private String name; private Address address; private Collection<Order> orders = new HashSet<Order>(); private Set<PhoneNumber> phones = new HashSet<PhoneNumber>(); public Customer() {} @Id public Long getId() { return id; } public void setId(Long id) { this.id = id; } public String getName() { return name; } public void setName(String name) { this.name = name; } public Address getAddress() { return address; } public void setAddress(Address address) { this.address = address; } @OneToMany public Collection<Order> getOrders() { return orders; } public void setOrders(Collection<Order> orders) { this.orders = orders; } @ManyToMany public Set<PhoneNumber> getPhones() { return phones; } public void setPhones(Set<PhoneNumber> phones) { this.phones = phones; } }
- 42. entity Customer { id Long id String name Address address onetomany Collection<Order> orders manytomany Set<PhoneNumber> phones }
- 45. com.springsource.roo.pizzashop roo> entity --class ~.domain.Topping --testAutomatically ~.domain.Topping roo> field string --fieldName name --notNull --sizeMin 2 ~.domain.Topping roo> entity --class ~.domain.Base --testAutomatically ~.domain.Base roo> field string --fieldName name --notNull --sizeMin 2 ~.domain.Base roo> entity --class ~.domain.Pizza --testAutomatically ~.domain.Pizza roo> field string --fieldName name --notNull --sizeMin 2 ~.domain.Pizza roo> field number --fieldName price --type java.lang.Float ~.domain.Pizza roo> field set --fieldName toppings --type ~.domain.Topping ~.domain.Pizza roo> field reference --fieldName base --type ~.domain.Base ~.domain.Pizza roo> entity --class ~.domain.PizzaOrder --testAutomatically ~.domain.PizzaOrder roo> field string --fieldName name --notNull --sizeMin 2 ~.domain.PizzaOrder roo> field string --fieldName address --sizeMax 30 ~.domain.PizzaOrder roo> field number --fieldName total --type java.lang.Float ~.domain.PizzaOrder roo> field date --fieldName deliveryDate --type java.util.Date ~.domain.PizzaOrder roo> field set --fieldName pizzas --type ~.domain.Pizza
- 46. LAYERS
- 47. ABSTRACTION
- 48. ONE SIZE FITS ALL?
- 49. Know your toolbox, be creative and have fun! Thank you!
Notas del editor
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n