[jira] Updated: (TAP5-830) SpringModuleDef unnecessarily hard-codes that the type of object stored in the context is a ConfigurableWebApplicationContext when any object implementing ApplicationContext is sufficient

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

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

Howard M. Lewis Ship updated TAP5-830:
--------------------------------------

    Summary: SpringModuleDef unnecessarily hard-codes that the type of object stored in the context is a ConfigurableWebApplicationContext when any object implementing ApplicationContext is sufficient  (was: Non generalized interface usage in SpringModuleDef)

> SpringModuleDef unnecessarily hard-codes that the type of object stored in the context is a ConfigurableWebApplicationContext when any object implementing ApplicationContext is sufficient
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-830
>                 URL: https://issues.apache.org/jira/browse/TAP5-830
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-spring
>    Affects Versions: 5.1.0.5
>            Reporter: Andrey Larionov
>            Assignee: Howard M. Lewis Ship
>
> In SpringModuleDef exists private method locateExternalContext. It has
> return type of ConfigurableWebApplicationContext. But its calls only
> from contructor where assignment occurs to variable with type of
> ApplicationContext.
> It highly limits me on programmaticaly creating server context and
> passing into it SpringContext without implementing
> ConfigurableWebApplicationContext.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.