Hi Danilo, from my (limited) experience with Blossom, I'd say with Blossom you move the responsibility for selecting the right template away from Magnolia's mechanism to Spring's ViewResolver logic.
You can chain view resolvers in your Blossom configuration, so one possibility would be to get the file extension from the request in incorporate it into your view name somehow, so that the right view resolver is used. > Or it will work mapping the > extension in the various methods' annotations? Yes, that should also work, if you just put the whole path incl. extension in the RequestMapping annotation. Hth, Lutz On Thu, Jul 28, 2011 at 10:11 AM, Danilo Ghirardelli <[email protected]> wrote: > > Hi everybody, > is there in Blossom the possibility to define subTemplates just like in the > node definition? I know that you can always do a check for the extension and > switch in the code of the template itself, but in some cases the tree > configuration seems cleaner for this part. Or it will work mapping the > extension in the various methods' annotations? > > Regards, Danilo. > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
