[
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 SpringModuleDef is wired to WebApplicationContext but doesn't
use features not present in ApplicationContext, but this makes it impossible to
use for a context defined on the classpath. (was: SpringModuleDef use
webapplicationcontext ,not use ApplicationContext interface.)
You'd probably want to override TapestryFilter directly, rather than subclass
TapestrySpringFilter; as you can see, the source is very, very simple and in
your case (using a classpath ApplicationContext instead of the standard Spring
web initialization), even simpler.
> The SpringModuleDef is wired to WebApplicationContext but doesn't use
> features not present in ApplicationContext, but this makes it impossible to
> use for a context defined on the classpath.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> 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
>
> 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]
