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 (Closed) (JIRA)" <ji...@apache.org> on 2011/10/17 22:51:12 UTC

[jira] [Closed] (TAP5-1041) Cannot use existing Spring definition with GenericWebApplicationContext

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

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

    Resolution: Duplicate
      Assignee: Howard M. Lewis Ship

This was fixed as TAP5-830.
                
> Cannot use existing Spring definition with GenericWebApplicationContext
> -----------------------------------------------------------------------
>
>                 Key: TAP5-1041
>                 URL: https://issues.apache.org/jira/browse/TAP5-1041
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-spring
>    Affects Versions: 5.0.19
>            Reporter: Phil Zoio
>            Assignee: Howard M. Lewis Ship
>
> SpringModuleDef.locateExternalContext has following code:  
>       ConfigurableWebApplicationContext context = (ConfigurableWebApplicationContext) servletContext.getAttribute(
>                 WebApplicationContext.ROOT_WEB_APPLICATION_CONTEXT_ATTRIBUTE);
> This means you cannot use existing contexts based on GenericWebApplicationContext, which is the recommended WebApplicationContext class to use when constructing your application context programmatically. See the API docs: http://static.springsource.org/spring/docs/3.0.0.M2/javadoc-api/org/springframework/web/context/support/GenericWebApplicationContext.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira