[jira] [Updated] (TAP5-1897) tapestry-spring does not work with external spring contexts that include parents

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade updated TAP5-1897:
---------------------------------
    Labels: bulk-close-candidate  (was: )

This issue affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent version of Tapestry (currently 5.4.0, available from Maven Central), please update it as soon as possible and add '5.4.0') to the issue's affected versions.

> tapestry-spring does not work with external spring contexts that include parents
> --------------------------------------------------------------------------------
>
>                 Key: TAP5-1897
>                 URL: https://issues.apache.org/jira/browse/TAP5-1897
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-spring
>    Affects Versions: 5.3.2
>            Reporter: Fernando Padilla
>            Priority: Blocker
>              Labels: bulk-close-candidate
>
> I am using the spring ContextLoaderListener to build my external spring context, and also using the parentContextKey to bind a parent spring context to the default one constructed from applicationContext.xml.  But it looks like there was a recent change made to SpringModule that it will ignore beans that are defined in a parent spring context; which breaks our setup.  Could we please find a solution so we can bring in beans from parent contexts appropriately as tapestry once used to?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)