tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Schmitt (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-1522) Tapestry-spring does not support using Spring JavaConfig (AnnotationConfigWebApplicationContext)
Date Thu, 02 Feb 2012 11:31:53 GMT

    [ https://issues.apache.org/jira/browse/TAP5-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198703#comment-13198703

Markus Schmitt commented on TAP5-1522:

I found a workaround for that issue:

Defining one spring beans configuration file:

  Here you can either declare a component-scan with the root package of the Config class that
  the @Configuration annotation or a directly the bean that declares it.

      <context:annotation-config />

    	 base-package="org.yourcomp.yourapp.config" />
      <bean class="org.yourcomp.yourapp.conf.BeanWithAtConfiguration" />

So hereby we have a small xml config and the whole configuration starts with our main configuration

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


View raw message