[jira] Closed: (TAP5-1228) The need to configure the tapestry.alias-mode symbol makes it awkward to start a Registry up for unit testing purposes

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1228.
--------------------------------------

    Fix Version/s: 5.2.1
       Resolution: Fixed

> The need to configure the tapestry.alias-mode symbol makes it awkward to start a Registry up for unit testing purposes
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1228
>                 URL: https://issues.apache.org/jira/browse/TAP5-1228
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-hibernate
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.2.1
>
>
> 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).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.