You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2015/01/12 09:10:43 UTC
[jira] [Closed] (TAP5-1522) Tapestry-spring does not support using
Spring JavaConfig (AnnotationConfigWebApplicationContext)
[ https://issues.apache.org/jira/browse/TAP5-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Kemnade closed TAP5-1522.
--------------------------------
Resolution: Invalid
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.3.8 or the latest 5.4 preview release), feel free to provide the necessary information and reopen.
> Tapestry-spring does not support using Spring JavaConfig (AnnotationConfigWebApplicationContext)
> ------------------------------------------------------------------------------------------------
>
> Key: TAP5-1522
> URL: https://issues.apache.org/jira/browse/TAP5-1522
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-spring
> Affects Versions: 5.2
> Reporter: DI Florian Hackenberger
> Labels: bulk-close-candidate
> Attachments: java-config-support.patch
>
>
> Tapestry-spring currently requires that the context class extends TapestryApplicationContext. In order to use JavaConfig support (without going through an intermediate spring xml file), you would have to use AnnotationConfigWebApplicationContext as a base class and add the tapestry features on top (like TapestryApplicationContext does). Unfortunately that's impossible, as TapestryApplicationContext is not an interface.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)