You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2013/09/09 14:12:54 UTC
[jira] [Updated] (ISIS-520) Allow wicket viewer to be run in either
development or deployment mode by passing in the Isis --type cmd line arg.
[ https://issues.apache.org/jira/browse/ISIS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood updated ISIS-520:
-----------------------------
Description:
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 --type (-t) cmd line arg.
For simplicity, suggest:
- Isis SERVER = Wicket DEPLOYMENT mode
- Isis anything else = Wicket DEVELOPMENT mode
was:
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
> Allow wicket viewer to be run in either development or deployment mode by passing in the Isis --type cmd line arg.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: ISIS-520
> URL: https://issues.apache.org/jira/browse/ISIS-520
> Project: Isis
> Issue Type: Improvement
> Components: Viewer: Wicket
> Affects Versions: viewer-wicket-1.2.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: viewer-wicket-1.3.0
>
>
> 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 --type (-t) 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