You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jun Tsai (JIRA)" <de...@tapestry.apache.org> on 2007/05/17 08:56:16 UTC
[jira] Created: (TAPESTRY-1472) SpringModuleDef use
webapplicationcontext ,not use ApplicationContext interface.
SpringModuleDef use webapplicationcontext ,not use ApplicationContext interface.
---------------------------------------------------------------------------------
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Assigned: (TAPESTRY-1472) 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
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAPESTRY-1472:
----------------------------------------------
Assignee: Howard M. Lewis Ship
> 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
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-1472) 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.
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-1472) 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
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ 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: 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 (was: 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.)
> 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
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-1472) The module and filter are coded
against Spring's WebApplicationContext, but doesn't use any APIs not
present in ApplicationContext
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-1472) 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
Posted by "Jun Tsai (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497093 ]
Jun Tsai commented on TAPESTRY-1472:
------------------------------------
I have implement an spring integration.I use ObjectProvider.
see wiki:
http://wiki.apache.org/tapestry/SpringIntegrationInT505
> 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
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Closed: (TAPESTRY-1472) The module and filter are coded
against Spring's WebApplicationContext, but doesn't use any APIs not
present in ApplicationContext
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-1472.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.5
> 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
> Fix For: 5.0.5
>
>
> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org