You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Andrey Larionov (JIRA)" <ji...@apache.org> on 2009/08/31 12:24:32 UTC

[jira] Created: (TAP5-830) Non generalized interface usage4 in SpringModuleDef

Non generalized interface usage4 in SpringModuleDef
---------------------------------------------------

                 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


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.


[jira] Updated: (TAP5-830) Non generalized interface usage in SpringModuleDef

Posted by "Andrey Larionov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrey Larionov updated TAP5-830:
---------------------------------

    Summary: Non generalized interface usage in SpringModuleDef  (was: Non generalized interface usage4 in SpringModuleDef)

> Non generalized interface usage in SpringModuleDef
> --------------------------------------------------
>
>                 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
>
> 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.


[jira] Updated: (TAP5-830) Non generalized interface usage in SpringModuleDef

Posted by "Andrey Larionov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrey Larionov updated TAP5-830:
---------------------------------

    Summary: Non generalized interface usage in SpringModuleDef  (was: Non generalized interface usage4 in SpringModuleDef)

> Non generalized interface usage in SpringModuleDef
> --------------------------------------------------
>
>                 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
>
> 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.


[jira] Assigned: (TAP5-830) Non generalized interface usage in SpringModuleDef

Posted by "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 reassigned TAP5-830:
-----------------------------------------

    Assignee: Howard M. Lewis Ship

> Non generalized interface usage in SpringModuleDef
> --------------------------------------------------
>
>                 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.


[jira] Assigned: (TAP5-830) Non generalized interface usage in SpringModuleDef

Posted by "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 reassigned TAP5-830:
-----------------------------------------

    Assignee: Howard M. Lewis Ship

> Non generalized interface usage in SpringModuleDef
> --------------------------------------------------
>
>                 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.


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

Posted by "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 closed TAP5-830.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.2.0

> SpringModuleDef unnecessarily hard-codes that the type of object stored in the context as 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
>             Fix For: 5.2.0
>
>
> 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.


[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

Posted by "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.


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

Posted by "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 closed TAP5-830.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.2.0

> SpringModuleDef unnecessarily hard-codes that the type of object stored in the context as 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
>             Fix For: 5.2.0
>
>
> 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.


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

Posted by "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 as a ConfigurableWebApplicationContext when any object implementing ApplicationContext is sufficient  (was: SpringModuleDef unnecessarily hard-codes that the type of object stored in the context is a ConfigurableWebApplicationContext when any object implementing ApplicationContext is sufficient)

> SpringModuleDef unnecessarily hard-codes that the type of object stored in the context as 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.


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

Posted by "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 as a ConfigurableWebApplicationContext when any object implementing ApplicationContext is sufficient  (was: SpringModuleDef unnecessarily hard-codes that the type of object stored in the context is a ConfigurableWebApplicationContext when any object implementing ApplicationContext is sufficient)

> SpringModuleDef unnecessarily hard-codes that the type of object stored in the context as 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.


[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

Posted by "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.