Multi-site support in Magnolia

Yet another week of development is nearly over (at least for me). What was this week all about? Apart from the really low temperatures outside (on Tuesday it was -24C at 4am), I focused mainly on extending the multi-site support in Magnolia. This feature exists for years already. But what it really means in context of Magnolia? In general you can setup the server to run mulptiple domains and you can configure such server to redirect to different subtree respective to what domain was the incoming traffic directed. The Magnolia part of the multi-site support allows you to assign different site (and theme) to each such subtree and can therefore make each site look and behave completely different. As normal in Magnolia you can of course also control the permissions for each subtree. So far so good. One might even ask, what else do you ever want from multi site support? Here's one thing that comes up quite often: hide the fact that each site is a subtree. Why? Many reasons. Spanning from shorter or nicer URLs to Search Engine Optimization. Until now, you could work around this issue the same way as a lot of other solutions do - externally, e.g. use a reverse proxy and/or mod_rewrite to hide the extra path and process all the content to rewrite links on the fly. During the course of last sprint we tried to make this internal to Magnolia without the need for outside solution. You can check out the trunk of Magnolia (or 4.3-m1 tag) to...

Date: January, 28 2010
Url: http://www.java.net/blog/rah003/archive/2010/01/28/multi-site-support-magnolia

Others News