[jira] [Closed] (TAP5-1191) How to use PageTester with web apps using tapestry-spring and Spring 3.0

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

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

Jochen Kemnade closed TAP5-1191.
--------------------------------
    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.

> How to use PageTester with web apps using tapestry-spring and Spring 3.0
> ------------------------------------------------------------------------
>
>                 Key: TAP5-1191
>                 URL: https://issues.apache.org/jira/browse/TAP5-1191
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-test
>    Affects Versions: 5.2
>            Reporter: Thomas Wintergerst
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> We am using Tapestry for a provisioning portal. The web portal is only a part of the complete application. The application uses Spring 3.0. As the web portal must use some of the core libraries we must use Tapestry v5.2.0-SNAPSHOT (hoping for a release soon), as only tapestry-spring-5.2.0-SNAPSHOT is compatible with Spring 3.0.
> I would like to use the PageTester to perform some tests relating to pages of the web portal. But unfortunately it seems not to be possible to instanciate pages that require injected Spring beans (in fact all pages in our web portal are based on Spring beans).
> The PageTester provides the method provideExtraModuleDefs() that perhaps could be used in a derived class to add an instance of SpringModuleDef (that is flagged "internal", of course). But the SpringModuleDef class requires a ServletContext as a constructor parameter. Within the context of the PageTester I have no access to such an object.
> Also adding SpringModule.class as the 4th parameter of the PageTester constructor does not work.
> Am I missing some point here? Or is it currently really not possible to use PageTester for page classes requiring injected Spring beans?



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