Hi list, Magnolia Blossom 1.1.1 has just been released.
This release fixes a few bugs and adds some valuable new features. * @Available for templates, use this annotation on a method in your template to control on what pages a template can be used. * Virtual URI Mapping, beans that implement VirtualURIMapper are detected and exposed in Magnolia. There's also a new way of creating uri mappings. Annotate a class with @VirtualURIMapper and its methods will be exposed as virtual uri mappings. * Multipart Support, the multipart processing that is done by Magnolia is now available from Spring. Documentation http://wiki.magnolia-cms.com/display/WIKI/Magnolia+Blossom Download https://sourceforge.net/projects/magnoliablossom/ Samples http://svn.magnolia-cms.com/svn/community/modules/blossom/samples/trunk/ Issue Tracker http://jira.magnolia-cms.com/browse/BLOSSOM Release Notes Small feature and bug fix release. The javadoc documentation has been greatly improved and extended. You can now annotate a method in your templates to control where the template is available. Blossom now also support multipart requests by exposing Magnolias built in support through the Spring APIs. VirtualURIMappings are now discovered and automatically exported. There's also support for declaring them using an annotation @VirtualURIMapper. Also, if you've done customizations to add more argument types to methods for creating and validating dialogs and tabs you'll be pleased to see that this extension point is now more comprehensible and easy to use. Added features: * BLOSSOM-1 Support for @Available to control where a template can be used * BLOSSOM-4 Support for exposing VirtualURIMappings and classes using @VirtualURIMapper * BLOSSOM-11 Support for multipart requests, bridges Springs abstraction onto Magnolia multipart processing Bug fixes: * BLOSSOM-5 NPE while detecting dialog factories and encounters abstract bean * BLOSSOM-7 ContextLoader is not released correctly on module reload * BLOSSOM-12 The autodetected node is created only when needed so it won't be considered as a dialog when its empty * BLOSSOM-13 Use of configNode when creating dialogs Behind the scenes: * BLOSSOM-8 Upgrade POM expand javadoc and pass checkstyle tests * BLOSSOM-9 Improve package structuring and extract detection of templates, paragraphs and dialogs to separate classes We'd like to thank everyone that has invested time in testing and providing feedback. Special thanks goes out to Danilo Ghirardelli, Thomas Duffey, Thomas Kalmar and Åke Argéus for your contributions. Tobias Mattsson Magnolia International Ltd. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
