Tapestry 5
  1. Tapestry 5
  2. TAP5-1228

The need to configure the tapestry.alias-mode symbol makes it awkward to start a Registry up for unit testing purposes

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 5.2.0
    • Fix Version/s: 5.2.1
    • Component/s: tapestry-hibernate
    • Labels:
      None

      Description

      To start Registry should be as simple as:

      registry = RegistryBuilder.buildAndStartupRegistry(TapestryModule.class);

      (or specify an AppModule.class as well)

      but that fails because tapestry.alias-mode is not defined.

      Tapestry should provide a default for tapestry.alias-mode so that it isn't necessary to create an extra module, such as:

      @SubModule(TapestryModule.class)
      public class TestingModule
      {
      public static void contributeFactoryDefaults(MappedConfiguration<String, String> configuration)

      { configuration.add(InternalSymbols.ALIAS_MODE, "servlet"); }

      }

      (of course, it's a question about if alias mode is even needed, once T5 finally gets portlet support; it's a hold-over from T4).

        Activity

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development