Somebody once said that the best ideas are the most simple ones.
Here comes one I had this morning when asked for example of page using this or that paragraph in Magnolia:
select * from nt:base where mgnl:template = 'stkTeaser'
It had been a while since we started to test Magnolia with ModeShape. It took few changes in the code here and there and it would not have happened if not for a big help from the JBoss folk.
End of the last year and beginning of this I've spent trying to get Magnolia work with ModeShape. There were issues with both of the apps. On one end, Magnolia had issues with the Modeshape session data refresh strategy, on the other one, Modeshape was sometimes stricter then JCR spec required it to be when it came to queries.
For anybody interested, we are giving a talk about repositories and content management in general on Thursday 12:30 at Hilton SF, Yosemite B. Session ID is S314239.
Feel free to drop by and ask also for Magnolia related questions should you have any. We have reserved some time also after the presentation should there be the need.
As it became almost a tradition we have rolled out next SwingX release just before the SwingLabs BOF at JavaOne last night.
I've just committed mavenized version of swingx under the swingx-r3734-mavenized branch.
If you know nothing about maven here's the basic:
As Karl mentioned already in his blog, SwingX 1.6.1 was released few weeks ago.
What I realized shortly after we put out Magnolia 4.3 is that while we tried to explain new multisite support for example in this screencast there are still plenty of grey areas and lot of confusion when people actually get to use the multisite support.
Have you got magnolia-4.3? Setup multiple sites? All right, you are all done. The only thing left is to observe the load on the server and how many requests you can serve. You might have noticed that after activating the content, load on the public is bit higher even though there is no increase in traffic.