tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-1897) tapestry-spring does not work with external spring contexts that include parents
Date Mon, 22 Aug 2016 06:48:22 GMT

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

Jochen Kemnade closed TAP5-1897.
--------------------------------
    Resolution: Incomplete

We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.4.1 or newer), feel free
to provide the necessary information and reopen.

> 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)

Mime
View raw message