There was a bunch of good things to see at this years Devoxx. My personal highlights are ScalaTest (you definitively want to look into this when testing concurrency in any java code ... the best way to test different race scenarios I've seen so far).
It's already five months since the version 1.0 have been announced at JavaOne. Today, new version of the SwingX have been released.
So it has began ... the first Magnolia Conference ever. And as a good omen, the conference planned for up to 80 participants is completely sold out. Considering the credit crunch and everybody trying to save a money, this seems as a very good sign of the attention the product commands.
For all of you who could not come to the SwingLabs session at JavaOne yesterday, here comes the announcement again:
After many broken promises and many delayes ... The SwingX 1.0 is released and available for download at SwingLabs download page.
Or can there ever be too many backups? I don't think so. On the other hand very often I have seen people underestimating testing their backup solutions and restore procedures and discovering issues only in middle of a crisis when restore of previously made backup is desperately (and quickly) needed.
Just few examples of those:
I might have mentioned something about cache in Magnolia here before, today let's look at another aspect of it.
While writing last entry I certainly didn't expect to be making another release in a week time. Nevertheless, here we go.
While not really planned originally, after a discussion in the forum, team has decided to push one more release before going for 1.0 and to take this oportunity for just one more sweep and cleanup of API. There were few other notable changes like cleanup of deprecated code and few more.
Over last couple of months more people have been asking about the workflow. Probably most often asked question is whether or not it is possible to monitor running workflow instances from within Magnolia. The response to this question have always been along the lines: yes, you can monitor the workflows, but no, you can't do so from within the admin interface of Magnolia.