Eclipse is more than an IDE; it is a host for a lot of great open-source runtime and framework technologies such as Eclipse OpenJ9, Eclipse DeepLearning4J, Eclipse Equinox, Eclipse RAP, Eclipse Jetty, the Eclipse Modeling Framework (EMF), Eclipse RCP, and the Eclipse 4 Application Platform (e4). Use this track when discussing Eclipse runtimes and frameworks.
When it comes to solving a problem the deep learning perspective is very different from the standard development approach. Instead of designing an algorithm to achieve a solution you find yourself looking at the data (preferably Big Data), trying to find out a good way to normalize them and to represent them, both as input and as output, in an effective way to the neural network.
Why reactive? How is MicroProfile related to reactive programming? There are many reactive Java libraries but they all work in a different way and provide different API. MicroProfile brings common reactive APIs that can be reused in many libraries to provide a unified experience for many Java developers. Including reactive operators, messaging, REST and more.
The default EMF code generation is based on JET templates and is not really configurable. To follow the good MDD practices, the code must be extended and the generated code must never be changed even if the EMF practices explain to use the @generated NOT annotations in the generated code.
This talk will explain and show how to use the genmodelAddon project available on the Eclipse market place and on GitHub.
Testing UI is usually tricky and is generally done only on the final application as validation tests.
Nevertheless a pure Eclipse 4 UI plugin (that can easily be mixed with other legacy Eclipse 3 plugins), provides POJOs that do not depend on any Eclipse RCP stack. In these conditions it is possible to mix different UI POJOs in a simple way so as to test their interactions (as integration tests).
If you know how to write Eclipse 3 UI plugins but you are not confident with the E4 writing, this talk is for you.
Pure E4 plugins can be fully mixed with legacy E3 plugins and there are no reasons today to still write legacy Eclipse 3 plugins while Eclipse 4 provides a lot of advantages.
This talk will compare in details the ways to write the UI code in Eclipse 3 vs Eclipse 4, without loosing the Eclipse 3 modularity while increasing testability.
This overview will focus on views, perspectives, editors, commands, preference pages and so on…
Are you a Java developer wondering what it means to have your application running in the cloud. This session will provide a peek into how the JVM is adapting to running in the cloud and what Java developers need to be aware to ensure they get the most of running in the cloud.
The session will pick an example spring application and tune it stage by stage at the end of which we have an application that is fully optimized and takes advantage of every aspect of the running in a cloud.
It includes the following stages
The motivation behind this talk is to provide insights on the performance and consumability for both languages. And also provide recommendations to developers and architects for different architectural combinations with these runtimes that work best for various modern workload scenarios.
Eclipse Platform 4.10 introduced “Link Handlers”. With that Eclipse platform can now handle custom URL schemes.
Handling of custom URL schemes in an application includes registering the application on operating system level. Link handlers take away all that operating system specific bourdon from you. You only need to implement you domain specific logic.
You are working on an existing Eclipse RCP application, an Eclipse 4 application or a tool based on Eclipse and want to know how to maintain, evolve and modernize it? Then this talk is for you!
Your Eclipse product is good enough to have license management, isn't it?
The Eclipse Passage project aims to provide rich and easily adaptable capabilities to define and control licensing constraints.