Tapestry
  1. Tapestry
  2. TAPESTRY-1472

The module and filter are coded against Spring's WebApplicationContext, but doesn't use any APIs not present in ApplicationContext

    Details

    • Type: Wish Wish
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.5
    • Fix Version/s: 5.0.5
    • Component/s: tapestry-spring
    • Labels:
      None
    • Environment:
      T5.0.5

      Description

      SpringModuleDef use WebApplicationContext to construct.why not use ApplicationContext interface?

      I want to override TapestrySpringFilter.My spring context is classpath xml application context.

        Activity

        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12568183 ] jira [ 12591264 ]
        Mark Thomas made changes -
        Workflow jira [ 12404165 ] Default workflow, editable Closed status [ 12568183 ]
        Howard M. Lewis Ship made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Fix Version/s 5.0.5 [ 12312477 ]
        Resolution Fixed [ 1 ]
        Howard M. Lewis Ship made changes -
        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 The module and filter are coded against Spring's WebApplicationContext, but doesn't use any APIs not present in ApplicationContext
        Howard M. Lewis Ship made changes -
        Assignee Howard M. Lewis Ship [ hlship ]
        Hide
        Jun Tsai added a comment -

        I have implement an spring integration.I use ObjectProvider.

        see wiki:

        http://wiki.apache.org/tapestry/SpringIntegrationInT505

        Show
        Jun Tsai added a comment - I have implement an spring integration.I use ObjectProvider. see wiki: http://wiki.apache.org/tapestry/SpringIntegrationInT505
        Howard M. Lewis Ship made changes -
        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.  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
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Summary SpringModuleDef use webapplicationcontext ,not use ApplicationContext interface. 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.
        Hide
        Howard M. Lewis Ship added a comment -

        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.

        Show
        Howard M. Lewis Ship added a comment - 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.
        Jun Tsai created issue -

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Jun Tsai
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development