Archive for the ‘magnolia’ Category
Nicolas and I adapted OpenWFE’s old XmlBeanCoder to JCR repositories (their most known implementation being Jackrabbit).
We’ve just wrote some documentation about that code.
Just a simple way of getting simple java beans in and out of JCRs; it’s useful for workflow workitems but also for anything that can be represented as a bean and has to be stored in a JCR.
The JcrBeanCoder is in use within the Magnolia CMS/DMS (3.0RC3).
The question is “how to store workitems within a JCR (Java Content Repository) ?”
The current implementation Magnolia uses serializes the workitem as an XML document which is placed within the JCR as a node (be indulgent with me about the names I use for those JCR concepts, they might not be exact).
I started writing this post, but meanwhile the perspective changed, we will adapt OpenWFE’s bean-to-xml code into some bean-to-jcr code. It will come handy for Magnolia’s workflow module and maybe for other parts of Magnolia.
A post as an echo to Boris’ post : Why OpenWFE ?
OpenWFE is within Magnolia now. They’re using the embedded version. Workflow participants are either Magnolia API commands or Magnolia roles.
The current task for OpenWFE there is playing the ‘activation workflow’, but the doors are open : anybody with a decent level of Magnolia and OpenWFE expertise may turn the bundle into a beautiful web-based business process management system.
Yet another OpenWFE incarnation : a musician in the Magnolia court.
His blog post about the talk. (There’ll be a few words about OpenWFE, as it’s the workflow engine embedded within Magnolia 3.0).
Floyd Marinescu ‘unlaunched’ his new Uber-Community site : InfoQ.
Alexandru Popescu (aka “The Mindstorm“) is one of his fellow ‘unlaunchers’.
I’m looking forward seeing this site grow and publish quality content… Hey, there’s even a welcome goodie : a book named “Java Transaction Design Strategies” (available as a free PDF download), 188 pages on java transactions.
Congratulations to the InfoQ team !
I had kept it open for ‘anonymous’ posters (nobody), but now after only two spam posts (in only one week), I decided to close it, allowing only sf.net users to post on it.
I can’t lose time at deleting/excluding such messages every day. Sorry, John Doe, you’ll have to set up an sf.net account.
The second version of the OpenWFE website (first move to Confluence) fell regularly victim to wiki spam and other trolls. I don’t want to clean out such cruft day after day (especially in the unfriendly sf.net admin interfaces).
Breaking news : Magnolia 3.0, the content management suite, will be released on Thursday. It embeds OpenWFE as its workflow engine. It’s not only a [web] content management suite, but also a complete document management system.
I’ve uploaded OpenWFE 1.7.0pre3 jars.
It mainly features a <sleep> expression with an ‘until’ attribute that accepts various date formats. Previously it accepted only ISO 8601 formatted dates.
This feature was requested by the team integrating OpenWFE within the Magnolia CMS, a page or a set of page can thus get activated/published by the embedded OpenWFE at a certain point in time.
The move to subversion is a success. It allowed to rename lots of things very easily (without having to post support requests to the sf.net team).
I’m now working on making OpenWFE available through Maven. Again, the motivation is the integration within Magnolia which heavily uses Maven.
Another step in the short term will be the extraction of the participant-map parsing facility to an implementation of a ParticipantMapFactory. This was requested by Lukas, who is currently working on his master project : an OpenWFE IDE based on Eclipse RCP.
Having a meeting in Basel with Boris. Snow is falling heavily on Northern Switzerland.
And finally, we had some “primitivo”.
But wouldn’t an ‘open source strike’ simply show the huge extent of open source software ? It’s ubiquitous. Well… It could terminate lives (
kill -9 people), it’s not a good idea.