Skip to main content


Showing posts from 2006

Reuse or Rewrite AndroMDA Cartridges?

Someone asked me what is the best way to work with AndroMDA in case that the architecture (structure, naming, process, etc.) is different than the AndroMDA's one. Reuseall the cartridges as far as possible and extend them or rewritethem from scratch?

My opinions are as follow:
Think of a frameworkeverytime you use AndroMDA. This includes the cartridges AndroMDA offers. When you are using frameworks you mostly don't want to rewrite them. You want to reuse and extendthem. So, reuse and extend already available AndroMDA cartridges is the way to go.If your team is only a small teamnever think of building your own architecture, thus you don't need to rewrite the cartridges. By building your own architecture (e.g. using your own directory structure, using your own naming convention, etc.) you mostly need to write your own cartridges which is costly. Remember that the developers of AndroMDA and AndroMDA cartridges are not beginners. They had many thoughts poured into the cartridges…

Next year conference...

Next year at OOP 2007Frank and I will offer a session about MDA and product line engineering. In this session we'll show how to use MDA with product line techniques in a pragmatic wayby using Open Source Java products. We'll underline the importance of Business Rules, so that we will be able to build a flexible solution for some domains which is based on thesame business requirements.

This should be a practical session and not a theoretical one as often the case in product line sessions. I would also like to thank Gernot who made this session possible!

The Heavyweight Champions are... Springframework and Hibernate?

There are a lot of argumentations exist trying to proof whether a combination of Springframework and Hibernate is still a "lightweight" or already a "heavyweight" champion. Please see following discussions in TSS for some of arguments:
Ten Common Misconceptions about Spring Developing J2EE applications without Spring? Why?
My conclusions after working with Springframework and Hibernate in some of my projects are: yes, Springframework and Hibernate arealready ourheavyweight champions! Why?
It's getting on my nerves as I have to create SpringBeans by editing those Spring XML files. This is the same with Hibernate hbml files. I know there are some tools available (e. g. Spring and Hibernate plugins) to help me finish these annoying works. But still... at the end this is just the same as working with EJB 2.x with those deployment descriptors. You might say, I can use annotations. The problem is I still have to deploy …

MDA 2005

The most interesting discussion in year 2005 I've followed and joined sofar about MDA and the future of Java is this one at Beyond Java. More than 760 threads... with many interesting and great ideas...

Happy Anniversary Indonesia!

p.f. 17 August 2006 - 61 years

FYI: Java island is located in Indonesia... so if you want to learn Java language you need to know Indonesian language first :-)

This should be your first exercise...
Selamat Ulang Tahun Kemerdekaan Indonesia yang ke 61! Semoga selalu panjang umur! Untuk membaca pidato Presiden RI, silahkan untuk melihat artikel ini di KOMPAS: Pidato Presiden 17 Agustus 2006.

Jorn Bettin has written this comment on the "Standardisation of Model Driven Approach"

Jorn Bettin has written this comment on the "Standardisation of Model Driven Approach":

Also, beyond the realm of MDA, in relation to model driven approaches and the use of domain-specific languages in general, there is the question of when and to what degree will standardisation occur. Usually the more domain-specific a language can be made, the more value it adds. Yet, the closer a domain-specific language gets to capturing part of the competitive edge of an organisation, the less incentive for industry wide "standardisation".

From my point of view standardisation will only happen if we could get a direct positive impact from it. So, this is actually very pragmatic. A very good example is the use of AndroMDA. I could imagine that there are a lot of organisations out there - which are all the user of AndroMDA - which have standardised their "DSL" based on AndroMDA DSL elements like Entity, Service, tagged values, etc. Why? Because you get directly benefit…