Hi Marco, With blossom the controllers sit behind the rendering engine and are called when a piece of content should be rendered. At this point Magnolia has used the url to find the content and then the content is mapped to a controller using the path in @RequestMapping. Using path variables isn't meaningful because a path /cars/ferrari will result in a 404 when Magnolia can't find the content.
If you want /cars/ferrari to go directly to your controller instead of being processed by the rendering engine you need to set up a standard Spring DispatcherServlet to handle that path. There's instructions on how to do that in our wiki http://wiki.magnolia-cms.com/display/WIKI/Adding+a+DispatcherServlet+to+a+Blossom+module Should you want to pass information in the path to a component or template without it being used to map to content Magnolia has a feature called selectors that can come in handy. A selector sits in the path after the page name and before its extension. A delimiter character is used to indicate where the page name ends and the selector starts. The character is a tilde, ~. For instance /articles/article~selector.html. To get the selector in your code use MgnlContext.getAggregationState().getSelector(). For more information see https://wiki.magnolia-cms.com/display/DEV/Concept+-+selectors Hope that helps, Tobias -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=ced570d2-3bb4-4874-a481-a826abbc0b7d ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
