[
https://issues.apache.org/jira/browse/TAPESTRY-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship updated TAPESTRY-1472:
-------------------------------------------
Summary: The module and filter are coded against Spring's
WebApplicationContext, but doesn't use any APIs not present in
ApplicationContext (was: SpringModuleDef is coded against
WebApplicationContext but doesn't use features not present in
ApplicationContext; this makes it impossible to use for a context defined on
the classpath)
> The module and filter are coded against Spring's WebApplicationContext, but
> doesn't use any APIs not present in ApplicationContext
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1472
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1472
> Project: Tapestry
> Issue Type: Wish
> Components: tapestry-spring
> Affects Versions: 5.0.5
> Environment: T5.0.5
> Reporter: Jun Tsai
> Assignee: Howard M. Lewis Ship
>
> SpringModuleDef use WebApplicationContext to construct.why not use
> ApplicationContext interface?
> I want to override TapestrySpringFilter.My spring context is classpath xml
> application context.
--
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]
