You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/09/23 21:47:26 UTC

[jira] [Closed] (TAP5-1350) TapestryFilter should allow sub-classes to specify additional module classes, not just ModuleDefs

     [ https://issues.apache.org/jira/browse/TAP5-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1350.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.3
         Assignee: Howard M. Lewis Ship

> TapestryFilter should allow sub-classes to specify additional module classes, not just ModuleDefs
> -------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1350
>                 URL: https://issues.apache.org/jira/browse/TAP5-1350
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.2.5
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.3
>
>
> Currently, only this method is provided:
>     protected ModuleDef[] provideExtraModuleDefs(ServletContext context)
> The problem with this is that the @SubModule annotation is not supported by RegistryBuilder.add(ModuleDef) ... its supported by RegistryBuilder.add(Class...).
> An additional method:
>   protected Class provideExtraModuleClasses(ServletContext context);
> would fit the bill.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira