Tapestry 5
  1. Tapestry 5
  2. TAP5-1077

Merge symbol values into property values from a bean definition

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.5
    • Fix Version/s: 5.2.0
    • Component/s: tapestry-spring
    • Labels:
      None

      Description

      Springs allows you to externalize property values from a bean definition into a property file. It would be nice if the values of the property placeholders could be read from symbol values. An example:

      <bean id="serviceStrategy" class="$

      {custom.strategy.class}

      "/>

      public static void contributeApplicationDefaults(MappedConfiguration<String, String> configuration)

      { configuration.add("custom.strategy.class", "com.foo.DefaultStrategy"); }
      1. web.xml
        1 kB
        Brian Heston
      2. TapestrySpringFilter working.txt
        2 kB
        Brian Heston
      3. TapestrySpringFilter broken.txt
        7 kB
        Brian Heston
      4. database.properties
        0.2 kB
        Brian Heston
      5. ContextLoaderListener.txt
        4 kB
        Brian Heston
      6. applicationContext.xml
        2 kB
        Brian Heston

        Activity

        Igor Drobiazko created issue -
        Igor Drobiazko made changes -
        Field Original Value New Value
        Assignee Igor Drobiazko [ igor.drobiazko ]
        Igor Drobiazko made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Fix Version/s 5.2.0 [ 12314122 ]
        Resolution Fixed [ 1 ]
        Brian Heston made changes -
        Attachment TapestrySpringFilter working.txt [ 12442578 ]
        Attachment TapestrySpringFilter broken.txt [ 12442579 ]
        Attachment ContextLoaderListener.txt [ 12442580 ]
        Hide
        Brian Heston added a comment -

        The change made for this feature has broken existing Spring functionality regarding properties. I have a single project with Spring for the services and Tapestry for the presentation. The Spring beans that used to load properties from the properties files can no longer get their values. I have attached log output from the version before the update and the version with this update to illustrate the lack of Spring loading the properties files. I've also attached the config files used to reproduce the problem.

        Show
        Brian Heston added a comment - The change made for this feature has broken existing Spring functionality regarding properties. I have a single project with Spring for the services and Tapestry for the presentation. The Spring beans that used to load properties from the properties files can no longer get their values. I have attached log output from the version before the update and the version with this update to illustrate the lack of Spring loading the properties files. I've also attached the config files used to reproduce the problem.
        Brian Heston made changes -
        Attachment applicationContext.xml [ 12442582 ]
        Attachment web.xml [ 12442583 ]
        Attachment database.properties [ 12442584 ]
        Brian Heston made changes -
        Attachment ContextLoaderListener.txt [ 12442580 ]
        Brian Heston made changes -
        Attachment ContextLoaderListener.txt [ 12442586 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Closed Closed
        26d 21h 28m 1 Igor Drobiazko 21/Apr/10 07:33

          People

          • Assignee:
            Igor Drobiazko
            Reporter:
            Igor Drobiazko
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development