it systemloesungen OG, Andreas-Hofer-Strasse 22, 6067 Absam
We are pleased to announce that the whole moware framework is running on the newest
version of java, i.e version 8, now. Instead of revealing details here, have a look at the newest screenshots
taken from one of the major applications running on our stack.
Of course, no single line had to be changed in any of the applications in order to migrate to java 8 and the FX 8 Ui framework.
Instead we provide new features for the applications. We came up with inline table editing, improved hot-key control and a new design.
To push things even further, the whole stack is enabled to run on any web-application server. This allows us to bring in a brand
new html touch client next month. Developer still can code, test and run their apps as rich-client. However, optionally
they can also deploy the app to a server without changing anything but the configuration.
working for 3 years on our libraries to write desktop business applications,
have to download and install our libraries to get an impression of its
series "goodbye expensive software development" will be available in
problem areas of modern software development for custom applications,
Here a link to the issue: https://jaxenter.de/magazines/Java-Magazin-314-170797
going productive with some of our generated user-interfaces in java FX, we set
proposed workaround is not a single measure, but a whole series of steps to
ensure the cleanup.
(Pic 1: Cleanup code used)
applying this workaround in our TableForm component, we recognize a total heap
size of aprox.
Forms3 is our DSL to model user-interfaces for typical business applications on a logical level. Up to now, models were translated
by code generators to java-code using apache pivot as UI-library. With some help from our friends from bestsolution.at we recently
switched to the javaFX stack.
Since our DSL specifies user-interfaces in a pure logical form, i.e. without any dependencies on the underlying UI-library, we could
simply regenerate existing business-applications and run them in the javaFX environment.
JavaFX will allow us to take advantage of e(fx)clipse and the whole osgi-environment as future runtime for business-applications.
Furthermore, this was a first "prove of concept" that underlying technology stacks can be exchanged quite easily.
In Summer 2012 we used the mbeddr toolkit to generate C code out of modelled tests. mbeddr
supports embedded software development based on an extensible version of the C programming
language and an IDE. We recently wrote a case study, where we summarized our experiences made and
some lessons learned. Feel free to contact us for further information.
After almost two years of research we summarized the „status quo“ in a couple of slides (german only).
As described in the slides, we propose to develop enterprise applications around a few but very central concepts, i.e.
(1) Processes and Conditions
(2) commands and
Some explanations of the concepts and the supporting engineering-process can be found in the slides.
Our goal for Spring 2012 is to further develop the codegenerators to reach an initial release,
generating OSGi-packages and javaFX userinterface for fat-client usage.
We recently wrote a paper describing our two DSLs to model business applications. I attached a pdf version of the paper to this post. Hope there are some interesting thoughts for you. Feel free to contact me in case of questions.
Here is the paper! mps_showcase.pdf
Instead of discussing language modularization, -composition or -extension in theory, i am going to give you a brief
glimpse from a practical perspective by pointing out some major aspects of our business-application DSL´s: objectflow and
forms. Both DSL´s were built with jetbrains Meta Programming System. In this blog entry i will focus on objectflow since
we issued the first release of the DSL this week.
Objectflow builds on the ideas of Eric Evans´ paradigm of domain-driven design (DDD). Any data (entities or value objects
in DDD terms) can be modelled as objectflow business objects with various attributes and references. For example, an
invoice with invoice positions is modelled as a business object invoice containing a collection of invoice position business
objects. The invoice becomes a so called “root aggregate”, when functionality or operations are added in a dedicated invoice
service. Basically, all necessary functionality has to be put into a service and in turn, the service has to be related to a
business object. Thus, although Objectflow services can be written in plain java, the structure and building blocks of
services are standardized. Particularly this standardization results in more transparency and higher code quality by also incorporating
the flexibility of the java language itself.
Objectflow also takes advantage of a very strong collection language from MPS, which can be applied in services. Building
unions of invoices or summing up a collection of invoices are central operations in business and should therefore be
supported with a very clear and handy syntax. The collection language employed with objectflow provides the means to build
expressive queries using closures - in a way similar to Microsoft´s LINQ.
The very same high level collection language is also used in objectflow to handle database queries. Objectflow allows the
developer to create a so called “repository” containing various queries for business objects. Instead of generating java code,
SQL queries as well as their mappings to related database table fields with business object properties are generated automatically.
Thus the developer is no longer challenged by technical implementation details like mapping or database querying.
Of course, objectflow actively supports test driven development. Developers can create a new executable testsuit - tailored
to test business logic- with just one click. The testsuit contains pretest-data and posttest-data, both described in simple
json-notation. Pretest-data contains necessary data saved in business objects, which gets built and initialized before running a test.
Posttest-data contains expected outcomes which are compared with actual data from the test by posttest-checker methods.
To get a service tested, just shovel some pretest-data into a service and check it after execution with expected results.
In our initial case of invoices, one can test a booking services with a pretest invoice and posttest booking lines.
Feel free to contact me for further explanations. In the forthcomming blog entry, i am going to present some code examples
and screenshots from the forms DSL. See you soon...