Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Eclipse DemoCamps November 2008/Hamburg/Session Abstracts"
(→Abstract) |
(→Rethinking the Architecture of Java ORM in terms of LINQ) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | == Rethinking the Architecture of Java ORM in terms of LINQ == | + | == Rethinking the Architecture of Java ORM in terms of LINQ == |
| − | '''[http://www.sts.tu-harburg.de/~mi.garcia/ Miguel Garcia] (TUHH), [http://www.rakhu.blogspot.com/ Rakesh Prithiviraj] (TUHH)'''<br> | + | |
| + | '''[http://www.sts.tu-harburg.de/~mi.garcia/ Miguel Garcia] (TUHH), [http://www.rakhu.blogspot.com/ Rakesh Prithiviraj] (TUHH)'''<br> | ||
| + | [http://www.sts.tu-harburg.de/~mi.garcia/slides/ESE20081118LINQ4EMF.pdf (Slides)] <br> | ||
The general theme revolves around the efficient evaluation of LINQ queries in a Java-based implementation. Regarding the outline below, the first two items have already been reported in [1], the remaining ones are new. | The general theme revolves around the efficient evaluation of LINQ queries in a Java-based implementation. Regarding the outline below, the first two items have already been reported in [1], the remaining ones are new. | ||
| Line 31: | Line 33: | ||
After an introduction into our application domain, this talk will focus on our usage of OSGi and Eclipse technology. | After an introduction into our application domain, this talk will focus on our usage of OSGi and Eclipse technology. | ||
| + | |||
| + | == Plugin reuse and adaptation with Object Teams: Don't settle for a compromise! == | ||
| + | ''Stephan Herrmann, ([http://www.swt.tu-berlin.de TU Berlin])'' | ||
| + | |||
| + | When reusing existing plugins for something innovative, you're likely to do | ||
| + | things the original plugin author has not anticipated. This typically brings about | ||
| + | some kinds of compromise: | ||
| + | |||
| + | * You adjust your requirements to what the reused plugins provide. Thus you settle for a different product than you intended. | ||
| + | * Or, you refrain from reuse but develop everything from scratch, settling for much lower productivity. | ||
| + | * Or, you apply some brute force method (like copy&paste) to get your job done, but then you settle for a brittle design, that is a pain to maintain. | ||
| + | |||
| + | With [http://www.objectteams.org Object Teams] it is possible to eat the cake | ||
| + | ''(apply unanticipated adaptations by disciplined aspect bindings)'' | ||
| + | and still have it ''(sustain a well modularized, maintainable design)''. | ||
| + | [http://trac.objectteams.org/ot/wiki/OtEquinox OT/Equinox] brings | ||
| + | this power to the development of Eclipse plugins (Equinox bundles). | ||
| + | |||
| + | This demo will show several real world examples from the implementation of the | ||
| + | [http://www.objectteams.org/distrib/otdt.html OTDT] itself. | ||
| + | Included are adaptations of a variety of plugins like JDT, Debug, | ||
| + | PDE, JUnit, Workbench etc. | ||
Latest revision as of 13:50, 3 November 2008
Contents
Rethinking the Architecture of Java ORM in terms of LINQ
Miguel Garcia (TUHH), Rakesh Prithiviraj (TUHH)
(Slides)
The general theme revolves around the efficient evaluation of LINQ queries in a Java-based implementation. Regarding the outline below, the first two items have already been reported in [1], the remaining ones are new.
Outline
- LINQ set of technologies distilled. Architectural differences between JPA ORM and ADO.NET Entity Framework. Benchmarks for queries on large ORMed Ecore models
- LINQ-favored approach to runtime translation into the query language of the target persistent store
- Products and prototypes in the Java space aiming at LINQ functionality. We showcase the approach adopted by JaQue, which aims to adopt bytecode inspection to translate LINQ statements into the persistent store's native query language
- The venue we plan to follow for future work, building upon technologies developed in the projects Pathfinder and Ferry, both being developed at U Tübingen.
Resources
[1] Garcia M., Prithiviraj R. Rethinking the Architecture of O/R Mapping for EMF in terms of LINQ
[2] http://www.hookedonlinq.com/
Harald Wellmann, innovative systems GmbH (Harman/Becker Automotive Systems)
Abstract
While digital map data seem to be ubiquitous in the age of Google Maps and similar services, car navigation systems have special requirements for a navigation database regarding compactness and fast access.
For this reason, the compilation of a binary map database for a car navigation system from raw geodata is a complex process which may run for days or weeks on a grid of worker machines.
At Harman/Becker, we are developing a next generation map compiler codenamed Anaconda which supports new input and output formats and which is built on top of OSGi and numerous Open Source Java Components, including domain specific ones like Geotools and uDig, a platform for geodata visualization based on Eclipse RCP, as well as general purpose frameworks like Hibernate and GridGain.
After an introduction into our application domain, this talk will focus on our usage of OSGi and Eclipse technology.
Plugin reuse and adaptation with Object Teams: Don't settle for a compromise!
Stephan Herrmann, (TU Berlin)
When reusing existing plugins for something innovative, you're likely to do things the original plugin author has not anticipated. This typically brings about some kinds of compromise:
- You adjust your requirements to what the reused plugins provide. Thus you settle for a different product than you intended.
- Or, you refrain from reuse but develop everything from scratch, settling for much lower productivity.
- Or, you apply some brute force method (like copy&paste) to get your job done, but then you settle for a brittle design, that is a pain to maintain.
With Object Teams it is possible to eat the cake (apply unanticipated adaptations by disciplined aspect bindings) and still have it (sustain a well modularized, maintainable design). OT/Equinox brings this power to the development of Eclipse plugins (Equinox bundles).
This demo will show several real world examples from the implementation of the OTDT itself. Included are adaptations of a variety of plugins like JDT, Debug, PDE, JUnit, Workbench etc.