I’m still have some hope that someone in Oracle will open its eyes and understand their mistake… I’m too much of an idealist .

The JVM has (had?) a really strong future as the number one cross platform VM – it’s utility extends far beyond the java language itself.

By closing the shop like this to try and license VMs on mobiles they may well find they damage that future and in the long term those lovely enterprise revenue streams as alternative technologies look more attractive.

Oh and see:

https://github.com/greedy/scala/

for scala on LLVM efforts. There’s also a scala effort on .Net too. They’re both some way off the JVM implementation but they will catch up as the language matures.

My team attempts to steer in a more domain-driven direction, and having “view” logic such as OXM in a “model” class in the middle of my domain breaks the single-responsibility principle. Now my domain objects do their job, as well as “display” themselves.

You could, for example, do like raveman suggested and make the Annotations more “magic”. But should you? Alternatively, XStream allows programatic description of the XML mappings. I could, instead, create a class whose job it is to know how a particular domain aggregate maps to XML. Then, if I wanted a second mapping, all I have to do is create a second class. Assuming I’m using dependency injection, I now just have to ensure the right XML Generator is being injected to the right places, and my system doesn’t have to worry about it.

I find this pattern far easier to understand and maintain, and in my experience newcomers to a project seem to have an easier time too.