[magnolia-dev] [JIRA] (BLOSSOM-145) Support for areas with class inheritance

Wed, 16 Oct 2013 05:27:58 -0700

TLN created Improvement BLOSSOM-145
Issue Type: Improvement Improvement
Assignee: Tobias Mattsson
Created: 16/Oct/13 2:24 PM
Description:

The issue is best explained by an example:

@Controller
public class FooterCapablePage
{
	@Area(value="footer", title="Footer Area", maxComponents="1")
	@AvailableComponentClasses({
		PageFooterComponent.class,
	})
	@Controller
	public static class PageFooterArea
	{
		@RequestMapping("/footerCapablePage/footerArea")
		public String render()
		{
			return "areas/componentIterator";
		}
	}
}

@Template(id="vwm:articlePage", title="Article Page")
@Controller
public class ArticlePageTemplate extends FooterCapablePage
{
	@RequestMapping("/articlepage")
	public String handleRequest()
	{
		return "/pages/article";
	}
}

It would be great and avoid a lot of redundant code if /pages/article.jsp could use <cms:area name="footer"/> in this scenario, but currently that doesn't work (the area isn't rendered, no components can be put in it). Only if the area is defined in ArticlePageTemplate itself, Blossom will accept it.

Spring annotations like @ModelAttribute or some other Blossom annotations like @TabFactory support inheritance.

Thank you.
Project: Magnolia Blossom Module
Priority: Neutral Neutral
Reporter: TLN
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to