[
https://issues.apache.org/jira/browse/TAPESTRY-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567161#action_12567161
]
angerclown commented on TAPESTRY-1778:
--------------------------------------
Probably a good idea to have provideExtraModuleDefs() in PageTester, regardless
of whether you need Spring or not.
I think that there should be also a SpringPageTester subclass that already does
the work needed for provideExtraModuleDefs(). I am not exactly sure how you
would pass in the data you need to providedExtraModuleDefs. For Spring, you
would need a list of file paths or Resource objects. Maybe the easiest, if
somewhat inelegant way, would be to just read a system parameter and parse the
String.
> Allow extending the PageTester with extra modules for better integration with
> tapestry-spring
> ---------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1778
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1778
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core, tapestry-spring
> Affects Versions: 5.0.5
> Reporter: Ivan Dubrov
> Attachments: pagetester.patch
>
>
> The problem is that when PageTester creates the registry it does not adds
> SpringModuleDef to the list of modules and all Spring services are
> unavailable because of this. Extending the PageTester is not possible as
> well, so you cannot extend it and provide additional module (like the
> TapestrySpringFilter does), so you have to copy-paste the complete PageTester
> and add a single line to include SpringModuleDef module to the list.
> I suggest adding the method similar to the
> TapestryFilter#provideExtraModuleDefs() to the PageTester.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
