[jira] [Updated] (ISIS-520) Allow wicket viewer to be run in either development or deployment mode by passing in the Isis --deploymentType cmd line arg.

["Dan Haywood (JIRA)" <ji...@apache.org>]

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

Dan Haywood updated ISIS-520:
-----------------------------

    Component/s: Viewer: Wicket
    
> Allow wicket viewer to be run in either development or deployment mode by passing in the Isis --deploymentType cmd line arg.
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ISIS-520
>                 URL: https://issues.apache.org/jira/browse/ISIS-520
>             Project: Isis
>          Issue Type: Improvement
>          Components: Viewer: Wicket
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>
> Isis' deploymentType configuration parameter declares EXPLORATION, PROTOTYPING and SERVER as three modes of operation; broadly speaking, "SERVER" corresponds to production.
> Wicket, meanwhile, has its configurationType which takes values of "DEVELOPMENT" or "DEPLOYMENT".
> Currently the Wicket viewer reads the Wicket "configurationType" init-param, and infers the Isis deploymentType from it.
> However, it would also be useful to go the other way, so that running the app through the org.apache.isis.WebServer (ie jetty) would honour the --deploymentType cmd line arg.
> For simplicity, suggest:
> - Isis SERVER = Wicket DEPLOYMENT mode
> - Isis anything else = Wicket DEVELOPMENT mode

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira